Date: Mon, 26 Aug 2013 07:38:43 -0700 From: Peter Grehan <grehan@freebsd.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: CFT: nested page table integration with amd64/pmap Message-ID: <521B6873.4070007@freebsd.org> In-Reply-To: <kvfemd$9i6$1@ger.gmane.org> References: <CAFgRE9H2n63%2B3GFwWNwE-Zu3gHPBcWhD4g6frB_ksXz=HAXp5w@mail.gmail.com> <kv7dig$id5$1@ger.gmane.org> <5217DAB2.3020204@freebsd.org> <kvfemd$9i6$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?521B6873.4070007>