From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: Proposed new "memory capacity claim"
	hypercall/feature
Date: Tue, 6 Nov 2012 14:23:39 +0100
Message-ID: <1352208219.12977.4.camel@hastur.hellion.org.uk>
References: <50939A1502000078000A5F61@nat28.tlf.novell.com>
	<CCB94326.50E8F%keir@xen.org>
	<7481128d-3f65-4cc3-ad96-1d4e9cd25094@default>
	<20121104203532.GA11377@ocelot.phlegethon.org>
	<26f55aab-7523-4681-9a61-a5e5740d43a9@default>
	<1352111399.25014.101.camel@hastur.hellion.org.uk>
	<5517445d-ed2e-4592-9a2b-98fc612f1ae8@default>
	<1352154288.7253.25.camel@hastur.hellion.org.uk>
	<8bec0df2-cf4b-4dcf-bbb8-121357a29d52@default>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <8bec0df2-cf4b-4dcf-bbb8-121357a29d52@default>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Olaf Hering <olaf@aepfle.de>, "Keir (Xen.org)" <keir@xen.org>, Konrad Wilk <konrad.wilk@oracle.com>, George Dunlap <George.Dunlap@eu.citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "Tim (Xen.org)" <tim@xen.org>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, George Shuklin <george.shuklin@gmail.com>, DarioFaggioli <raistlin@linux.it>, Jan Beulich <JBeulich@suse.com>, Kurt Hackel <kurt.hackel@oracle.com>, Zhigang Wang <zhigang.x.wang@oracle.com>
List-Id: xen-devel@lists.xenproject.org

On Mon, 2012-11-05 at 22:58 +0000, Dan Magenheimer wrote:
> It's not necessary to choose the _optimal_ fit, only a probable one. 

I think this is the key point which I was missing i.e. that it doesn't
need to be a totally accurate answer. Without that piece it seemed to me
that you must already have the more knowledgeable toolstack part which
others have mentioned.

Ian.