Gregory Haskins wrote: >> Note that as long as the apic code is in userspace, the sending side is >> also in userspace, so all the IPI related stuff doesn't touch the kernel. >> > > > I see. So really the entire approach I took (against the kernel code) is > wrong, and I should focus on the QEMU side? >
Well, eventually we do want to have the apic in the kernel, and we do want inexpensive inter-vcpu (and driver->vcpu) interrupts. But it seems that the simplest way to get things going is in qemu. Note that it's not enough; there's the mmu to harden for smp and basic support for creating > 1 vcpus. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- 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
