On Wed, Sep 24, 2008 at 02:10:26PM +0300, Avi Kivity wrote: > Glauber Costa wrote: >>> You can't coalesce the registers which trigger device action. You'll >>> destroy latency and/or functionality. >>> >> >> which kills the goal of getting rid of explicit kvm code. >> >> > > It's a fact that coalescing helps kvm but not qemu. > >> So maybe the solution here is to add calls in qemu to a memory >> coalescing function that in the raw qemu / kqemu case just don't >> do anything? >> > > That's just word games. s/kvm/qemu/ won't change the fact that this is > a kvm specific hook. Any ideas about what's up for the other hypervisors that may (we hope) be integrated in the future? Xen?
-- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
