From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: Ian.Campbell@citrix.com, konrad.wilk@oracle.com, keir@xen.org,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume
Date: Thu, 14 Jul 2011 12:26:28 +0200 [thread overview]
Message-ID: <20110714102628.GA9157@aepfle.de> (raw)
In-Reply-To: <4E1DB9C70200007800072DCC@nat28.tlf.novell.com>
On Wed, Jul 13, Jan Beulich wrote:
> >>> Ian Campbell <Ian.Campbell@citrix.com> 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.
Olaf
next parent reply other threads:[~2011-07-14 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E1DB9C70200007800072DCC@nat28.tlf.novell.com>
2011-07-14 10:26 ` Olaf Hering [this message]
2011-07-15 8:32 ` [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume Jan Beulich
[not found] <4E20873F020000780007307B@nat28.tlf.novell.com>
2011-07-15 18:23 ` Keir Fraser
2011-07-18 7:05 ` Jan Beulich
2011-07-18 7:27 ` Keir Fraser
2011-07-18 8:31 ` Ian Campbell
2011-07-18 8:47 ` Jan Beulich
2011-07-18 9:05 ` Ian Campbell
2011-07-18 9:50 ` Jan Beulich
[not found] <20110701104148.GA32729@aepfle.de>
[not found] ` <20110712164342.GA12867@aepfle.de>
2011-07-12 18:11 ` Konrad Rzeszutek Wilk
2011-07-13 9:12 ` Ian Campbell
2011-07-13 13:20 ` Konrad Rzeszutek Wilk
2011-07-15 8:56 ` Jan Beulich
2011-07-15 16:05 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110714102628.GA9157@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=jbeulich@novell.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox