>we should move all the PICs into KVM proper - and that includes the
>i8259A PIC too. Qemu-space drivers are then wired to pins on these
PICs,
>but nothing in Qemu does vector generation or vector prioritization -
>that task is purely up to KVM. There are mixed i8259A+lapic models
>possible too and the simplest model is to have all vector handling in
>KVM.
>
>any 'cut' of the interface to allow both qemu and KVM generate vectors
>is unnecessary (and harmful) complexity. The interface cut should be at
>the 'pin' level, with Qemu raising a signal on a pin and lowering a
>signal on a pin, but otherwise not dealing with IRQ routing and IRQ
>vectors.
>
>       Ingo

Actually that the best cut, it's not a cut that was chosen because of
someone's implementation status. It is the best logical way doing
things. 
It's either all of the components are in user space or in kernel space
altogether. Since PV drivers and APIC acceleration (vt/svm) are strong
arguments in favor of kernel implementation we should aim towards that.

It is also a very clean cut and it will predicting the exact interface
is easy.

>
>-----------------------------------------------------------------------
--
>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=DEVD
EV
>_______________________________________________
>kvm-devel mailing list
>kvm-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/kvm-devel

-------------------------------------------------------------------------
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

Reply via email to