* Avi Kivity <[EMAIL PROTECTED]> wrote:
> - *pic in kernel: most effort, easiest irq synchronization. Interface
> is pic/ioapic pin level, plus a topology description that userspace
> uses to tell the hardware how the pins are connected (logically
> required, but practically not).
yeah, that variant is the right way to do it. Note that this also paves
the way for possible future PIC hardware virtualization features like
the CPU directly injecting an external IRQ vector to the guest [without
trapping out to the hypervisor]. Interrupt handling fundamentally
belongs into the kernel, be that the host or the guest. (User-space
abstractions in the PIC space make little sense and i know of none.)
Ingo
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
