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>
Subject: Re: [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Thu, 14 Jul 2011 12:26:28 +0200
Cc: linux-kernel@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, keir@xxxxxxx, Ian.Campbell@xxxxxxxxxx, konrad.wilk@xxxxxxxxxx
Delivery-date: Thu, 14 Jul 2011 03:27:40 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1310639207; l=624; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=ws9xXoNSvimIywsqGdn6hwq0tWA=; b=QMwNbOuFMQOmUuMw92CSsgQuxliiLYZjFxQtsOn5UxuDk0xgP2KrAXSWpUg9sN19fO7 O5Z6nKPQs5Hu1VC97Nyge5h7RNwZZ2F18g1sUVACXnQqbDr1GrMHIyDPt7xaDRunGG1aH rMOu/jTnfX6o6+AizORC7NdKarYoENqGR4k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E1DB9C70200007800072DCC@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>
References: <4E1DB9C70200007800072DCC@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21.rev5535 (2011-07-01)
On Wed, Jul 13, Jan Beulich wrote:

> >>> Ian Campbell <Ian.Campbell@xxxxxxxxxx> 07/13/11 11:12 AM >>>
> >It's not so much an objection to this patch but this issue seems to have
> >been caused by Xen cset 20892:d311d1efc25e which looks to me like a
> >subtle ABI breakage for guests. Perhaps we should introduce a feature
> >flag to indicate that a guest can cope with the m2p changing size over
> >migration like this?
> Indeed - migration was completely beyond my consideration when
> submitting this. A feature flag seems the right way to go to me.

I will prepare a patch for a new feature flag.


Xen-devel mailing list