From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olaf Hering <olaf@aepfle.de>, linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume
Date: Tue, 12 Jul 2011 14:11:18 -0400 [thread overview]
Message-ID: <20110712181118.GA18662@dumpdata.com> (raw)
In-Reply-To: <20110712164342.GA12867@aepfle.de>
On Tue, Jul 12, 2011 at 06:43:42PM +0200, Olaf Hering wrote:
>
> Migration of pv guests fails, the guest crashes on the target host once the
> guest is unpaused after transit. It happens when the guest is started on a
> small systen, then migrated from that small system to a large system.
> If the guest is started on a large system, then migrated to a small system and
> back to the large system, the migration will be successful.
>
> The issue is that mfn_to_pfn() makes use of machine_to_phys_order, which
> is only configured once early in the boot process. After migration to a
> large host the mfns will exceed the order from the small system and a
> wrong code path is taken.
>
> Calling xen_setup_machphys_mapping() again in the resume path will avoid
> the crash.
Oh, duh!
Let me queue that up for 3.0-rc7 unless there are objections?
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
>
> ---
> arch/x86/xen/mmu.c | 2 +-
> arch/x86/xen/suspend.c | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> Index: linux-3.0-rc7/arch/x86/xen/mmu.c
> ===================================================================
> --- linux-3.0-rc7.orig/arch/x86/xen/mmu.c
> +++ linux-3.0-rc7/arch/x86/xen/mmu.c
> @@ -1623,7 +1623,7 @@ static void __init xen_map_identity_earl
> set_page_prot(pmd, PAGE_KERNEL_RO);
> }
>
> -void __init xen_setup_machphys_mapping(void)
> +void xen_setup_machphys_mapping(void)
> {
> struct xen_machphys_mapping mapping;
> unsigned long machine_to_phys_nr_ents;
> Index: linux-3.0-rc7/arch/x86/xen/suspend.c
> ===================================================================
> --- linux-3.0-rc7.orig/arch/x86/xen/suspend.c
> +++ linux-3.0-rc7/arch/x86/xen/suspend.c
> @@ -43,6 +43,8 @@ void xen_arch_hvm_post_suspend(int suspe
>
> void xen_arch_post_suspend(int suspend_cancelled)
> {
> + xen_setup_machphys_mapping();
> +
> xen_build_mfn_list_list();
>
> xen_setup_shared_info();
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next parent reply other threads:[~2011-07-12 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110701104148.GA32729@aepfle.de>
[not found] ` <20110712164342.GA12867@aepfle.de>
2011-07-12 18:11 ` Konrad Rzeszutek Wilk [this message]
2011-07-13 9:12 ` [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume Ian Campbell
2011-07-13 13:20 ` Konrad Rzeszutek Wilk
2011-07-15 8:56 ` Jan Beulich
2011-07-15 16:05 ` Jan Beulich
[not found] <4E1DB9C70200007800072DCC@nat28.tlf.novell.com>
2011-07-14 10:26 ` Olaf Hering
2011-07-15 8:32 ` 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
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=20110712181118.GA18662@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--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