CFT: nested page table integration with amd64/pmap

[Peter Grehan]

>>   For time-sensitive situations, there's not a lot of options other than
>> forcing guest memory to be wired, since there isn't visibility into the
>> host without having o/s-specific "tools" that could communicate this
>> information to the hypervisor.
>
> Ok, that is how I understood it also, but I thought that maybe there was
> some way of telling which guest memory belongs to the kernel and only
> wire those pages.

  Not in a general way. That's where you need a hypervisor-specific 
module in the guest to pass on this info e.g. vmware-tools.

later,

Peter.