[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] pc: Clean up PIC-to-APIC IRQ path

From: Blue Swirl
Subject: Re: [Qemu-devel] [PATCH] pc: Clean up PIC-to-APIC IRQ path
Date: Sat, 3 Sep 2011 21:01:58 +0000

On Sat, Sep 3, 2011 at 7:53 PM, Anthony Liguori <address@hidden> wrote:
> On 08/31/2011 11:59 AM, Blue Swirl wrote:
>> On Wed, Aug 31, 2011 at 8:28 AM, Avi Kivity<address@hidden>  wrote:
>>> On 08/30/2011 10:19 PM, Blue Swirl wrote:
>>>>>  We need some kind of two phase restore. In the first phase all state
>>>>> is
>>>>>  restored; since some of that state drivers outputs that are input to
>>>>> other
>>>>>  devices, they may experience an edge, and we need to supress that.  In
>>>>> the
>>>>>  second phase edge detection is unsupressed and the device goes live.
>>>> No. Devices may not perform any externally visible activities (like
>>>> toggle a qemu_irq) during or after load because 1) qemu_irq is
>>>> stateless and 2) since the receiving end is also freshly loaded, both
>>>> states are already in synch without any calls or toggling.
>>> That makes it impossible to migrate level-triggered irq lines.  Or at
>>> least,
>>> the receiver has to remember the state, instead of (or in addition to)
>>> the
>>> sender.
>> Both ends probably need to remember the state. That should work
>> without any multiphase restores and transient suppressors.
>> It might be also possible to introduce stateful signal lines which
>> save and restore their state, then the receiving end could check what
>> is the current level. However, if you consider that the devices may be
>> restored in random order, if the IRQ line device happens to be
>> restored later, the receiver would still get wrong information. Adding
>> priorities could solve this, but I think stateless IRQs are the only
>> sane way.
> We shouldn't really use the term IRQ as it's confusing.  I like the term
> "pin" better because that describes what we're really talking about.
> qemu_irq is designed oddly today because is represents something that is
> intrinsically state (whether a pin is high or low) with an edge notification
> with the assumption that the state is held somewhere else (which is usually
> true).
> Modelling stateful pins is useful though for doing something like
> introspecting pin levels, supporting live migration, etc.
> The way this works in QOM right now is that the Pin object has a level state
> that can be queried but it also has the ability to register for
> notifications on level change.
> The edge change signal isn't registered until realize.  This means that you
> can connect all of the device models, restore all of the pin states, and
> then realize the device model all at once.  At the point of realize, all of
> the devices have the right pin levels so each device can add their edge
> change signals and read the incoming pins and respond accordingly.

Even if the devices read the input pins on restore, they shouldn't
make any changes to their output pins because that would propagate to
other devices. To handle this in non-chaotic way would need hacks to
each device, multiphase stuff, priorities or transient suppressors.
>From the device point of view, restoring is not a state change and no
edges should be seen at that moment.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]