From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xensource.com
Subject: Re: [RFC PATCH] fix 32-bit PAE bootup of Xen PV guests.
Date: Tue, 23 Nov 2010 16:18:01 -0500 [thread overview]
Message-ID: <20101123211801.GA29499@dumpdata.com> (raw)
In-Reply-To: <1290544896-20754-1-git-send-email-konrad.wilk@oracle.com>
On Tue, Nov 23, 2010 at 03:41:35PM -0500, Konrad Rzeszutek Wilk wrote:
> I was wondering if you could help me out. The git commit
> b40827fa7268fda8a62490728a61c2856f33830b ("x86-32, mm: Add an initial
> page table for core bootstrapping") crashes 32-bit PAE Xen PV guests.
>
> I am attaching an RFC patch that works around your patch, but honestly
> I was wondering if there is a better way to make this work for 2.6.37?
> Any recommendations?
Ignore this patch please. Ian's fix (
http://marc.info/?l=linux-kernel&m=128879861204118&w=2) is much cleaner.
prev parent reply other threads:[~2010-11-23 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 20:41 [RFC PATCH] fix 32-bit PAE bootup of Xen PV guests Konrad Rzeszutek Wilk
2010-11-23 20:41 ` [PATCH] xen/mmu, x86-32: Make swapper_pg_dir writeable before calling setup_arch Konrad Rzeszutek Wilk
2010-11-23 21:18 ` Konrad Rzeszutek Wilk [this message]
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=20101123211801.GA29499@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bp@alien8.de \
--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