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

[Xen-devel] Re: [PATCH][RFC] Support S3 for MSI interrupt in latest kernel dom0

>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 17.12.08 16:06 >>>
>On 17/12/2008 14:47, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
>>> Could Xen remember the MSI state automatically, as it does for IO-APIC
>>> presumably already? It knows what vectors are routed where at least, even if
>>> dom0 has to reprogram the PCI device itself.
>> That is what the map_guest_pirq() re-invocation is intended for - use the
>> already known (stored) MSI state to re-setup the device accordingly
>> (after all, msi_compose_msg() only depends on the vector information
>> to be able to reconstruct address and data fields).
>Why wait for map_guest_pirq() to be invoked to do this?

Otherwise we need a new hypercall here, since Xen cannot do this
completely on its own (it has to wait for Dom0 to bring the device out of
any suspend state it may itself be in). And it would allow restoring the
old mechanism in your (2.6.18) Dom0, just without the unmap-pirq
portion during suspend - instead of needing another full re-
implementation cycle.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.