Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem

[Bastian Blank <waldi@xxxxxxxxxx>]

On Fri, Mar 19, 2010 at 01:13:41PM +0100, Bastian Blank wrote:
> The real fix could be:
> - Allow the hypervisor to lock interrupts it uses. Zero would be in it by
>   default. The interrupt for the used serial interface would be added.
>   All other pins are free to be programmed by the kernel once.
> - Don't do register_gsi calls from the initial setup in the kernel if no
>   ACPI override is present, only setup the rest.

Okay, I think I found another problem. Currently the setup looks like
this:
- PHYSDEVOP_setup_gsi: set trigger and polarity, unmask pin
- PHYSDEVOP_map_pirq: map to pirq, set irq handler to guest

If an interrupt fires between this two calles, what happens?

Usually I would do the setup the other way around. This would also make
it possible to use the irq table to allow the kernel to only set IO-APIC
pins mapped to already properly registered interrupts.

Bastian

-- 
Change is the essential process of all existence.
                -- Spock, "Let That Be Your Last Battlefield", stardate 5730.2

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel