> But doesn't the interrupt code have to check all interrupt sources on a > shared line?
well technically the kernel just calls all handers. > That means checking the non-PV interrupt as well, which > involves a vmexit (for mmio read). ok I see what you mean. Yes agreed we should avoid sharing with one of those animals ;) (Shouldn't be hard since we control the bios, and it's always fake hardware anyway) > It is possible (Xen does it) to batch interrupt delivery so that > multiple interrupts can be delivered with one vmentry. So you get the > best of both worlds: one check for interrupt source, and one vmentry if > multiple interrupts have fired. check for interrupt source is really cheap. I bet it's cheaper than the hacks xen does. (xen does many things that in academic 1970's hypervisors were a win but aren't on modern hardware..) Don't get me wrong, batching is probably a win, just it shouldn't be too expensive in terms of overhead or you'll loose anyway over time. > -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
