* Anthony Liguori <[EMAIL PROTECTED]> wrote:
> > Keeping the apic in the kernel simplifies this with the cost of
> > maintaining an apic/pic implementation.
>
> Hrm, this is definitely starting to sound like a PITA to deal with.
> Maybe in-kernel platform devices are unavoidable :-/
yes, very much so. Not only are they unavoidable, they largely simplify
many aspects of KVM. Did anyone here ever have unreliable keyboard
emulation in qemu because /dev/rtc didnt allow 1024 Hz? Such basic
issues are just not present when timer emulation is done by the kernel.
The kernel abstracts away the actual hardware, and Qemu then uses this
abstract interfaces to create something that is specific. By moving
platform device emulation into KVM, much of that (unnecessary)
indirection goes away. Furthermore, scheduling and guest-interrupt
handling is something that is most naturally done in the host kernel -
any indirection is unnecessary fat that distracts from the core purpose
of building a first-class hypervisor subsystem.
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
