From owner-freebsd-virtualization@FreeBSD.ORG  Mon Aug 26 14:47:58 2013
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id F18B9FF6;
 Mon, 26 Aug 2013 14:47:58 +0000 (UTC)
 (envelope-from grehan@freebsd.org)
Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12])
 by mx1.freebsd.org (Postfix) with ESMTP id B23BE2933;
 Mon, 26 Aug 2013 14:47:58 +0000 (UTC)
Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57])
 by alto.onthenet.com.au (Postfix) with ESMTPS id E148D11F4E;
 Tue, 27 Aug 2013 00:38:49 +1000 (EST)
Received: from Peters-MacBook-Pro.local (c-67-161-27-37.hsd1.ca.comcast.net
 [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA)
 with ESMTP id BOE87698 (AUTH peterg@ptree32.com.au);
 Tue, 27 Aug 2013 00:38:49 +1000
Message-ID: <521B6873.4070007@freebsd.org>
Date: Mon, 26 Aug 2013 07:38:43 -0700
From: Peter Grehan <grehan@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ivan Voras <ivoras@freebsd.org>
Subject: Re: CFT: nested page table integration with amd64/pmap
References: <CAFgRE9H2n63+3GFwWNwE-Zu3gHPBcWhD4g6frB_ksXz=HAXp5w@mail.gmail.com>
 <kv7dig$id5$1@ger.gmane.org> <5217DAB2.3020204@freebsd.org>
 <kvfemd$9i6$1@ger.gmane.org>
In-Reply-To: <kvfemd$9i6$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-virtualization@freebsd.org
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 14:47:59 -0000

>>   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.