RE: [Xen-ia64-devel] consoles, iosapics, and device interrupts

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>From: Alex Williamson
>Sent: 2005年11月12日 0:27
>
>   Here's the problem (or at least the start of it); we don't seem to be
>getting any input into the ns16550 driver in the xen hypervisor.  Since
>I'm on an HP box that does not use legacy interrupts for serial lines,
>the interrupt comes in through an IOSAPIC.  We currently don't seem to
>have any support for external interrupts through IOSAPICs.  I thought
>about simply adding polling support to ns16550, but w/o any timer
>support in the hypervisor, that looks non-trivial.  So, I was thinking
>about pulling the IOSAPIC code over.  This means we'll have to iterate
>all the IOSAPICs in the MADT to discover where the GSIs are mapped just
>so we can poke the right one for the serial port.  We can't hide this
>one IOSAPIC RTE from the domains, but unless I missed something, we
>already have IOSAPIC sharing issues if we ever have multiple privileged
>domains with I/O anyway.  

Hi, Alex,
        I second your concern and actually that's the major reason for 
necessity to move IOAPIC ownership into Xen hypervisor and present a virtual 
interrupt controller model to domain. Tristan already made some experiment to 
get serial input/output in Xen, and similar discussion went on following links 
that you may like to look:
        
http://lists.xensource.com/archives/html/xen-ia64-devel/2005-11/msg00026.html
        
http://lists.xensource.com/archives/html/xen-ia64-devel/2005-10/msg00111.html

Thanks,
Kevin
>I'm leery to even get into all the issues
>surrounding setting up interrupt polarity and trigger based on the PCDP
>tables.
>
>   Does this sound like the right way to go?  I feel like I'm opening a
>can of worms by adding a dependency to an IOSAPIC RTE that we're
>eventually going to hand over to a domain that may clear the interrupt
>vector we want to enable.  Thoughts?  Thanks,
>
>       Alex
>
>--
>Alex Williamson                             HP Linux & Open Source Lab
>
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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