On Tue, 2007-07-24 at 09:59 +0300, Avi Kivity wrote: > However, you can probably work around that by not setting an rmap for > the kernel mappings, and instead have the guest teach the host where the > kernel page tables live. You'd only be left with shared libraries, > until the kernel can share page tables for them too.
Well, I already treat kernel mappings specially (effectively I know the guest's PAGE_OFFSET): they're kept identical in all the 4 shadows, and need explicit guest flushing. Whether the guest shares (non-kernel) page tables or not, I will shadow them dumb as separate page table pages the way things stand. So, yes, shared libs will be my main issue. Address space randomization means I can't even use a heuristic such as looking for the page at the same address in other shadows. I'll come up with something. Anyway, virtio what I'm *supposed* to be doing today... Thanks, Rusty. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
