This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume

To: Jan Beulich <JBeulich@xxxxxxxxxx>, <Ian.Campbell@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, <keir@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Mon, 18 Jul 2011 08:27:06 +0100
Cc: olaf@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Mon, 18 Jul 2011 00:27:51 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=CcY2B4wnbfUPWwI1atM7Qakn8I7mJ13IPrO1VJM3gMI=; b=Sybi16ZlVSLcphKK4LosybcVpaGrMJkwbDxiPiGXrXEIjETq3U7nKD2i+LVXtcyKq0 iPH/dEaw3/mXU352FFaoR9OQQcbVSffOIijCxA1DNgNbNZbUcvitkDO2e3Rulvc3IQSX Mmh3d178jwfHHa6v+ebi4UzuJdGiWKPBsAPxA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E23F76D020000780004DCD9@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxFHBiKppVrRXHQekynmz773MeOdA==
Thread-topic: [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume
User-agent: Microsoft-Entourage/
On 18/07/2011 08:05, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>>>> On 15.07.11 at 20:23, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>> On 15/07/2011 18:30, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>>> Actually, one more thought: What's the purpose of this hypercall if
>>> it is set in stone what values it ought to return? Isn't a guest using
>>> it (supposed to be) advertising that it can deal with the values being
>>> variable (and it was just overlooked so far that this doesn't only
>>> include varying values from boot to boot, but also migration)? Or in
>>> other words, if we found a need to relocate the M2P table or grow
>>> its static maximum size, it would be impossible to migrate guests
>>> from an old to a new hypervisor.
>> Fair point. There has to be a static fallback set of return values for old
>> guests.
> Hmm, in my reading the two sentences sort of contradict each other.
> That is, I'm not certain what route we want to go here: Keep things
> the way they are after 23706:3dd399873c9e, and introduce a
> completely new discovery mechanism if we find it necessary to change
> the M2P table's location and/or size, including a mechanism for a guest
> to announce it's capable of dealing with that? If so, I think we ought
> to add a comment to the hypercall implementation documenting that
> its return values must not be changed (and why).

We can return different values from the existing hypercall if that is
negotiated with the guest, at run time or build time.

 -- Keir

> Jan

Xen-devel mailing list