From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Ian Campbell <Ian.Campbell@citrix.com>,
Borislav Petkov <bbpetkov@yahoo.de>
Subject: Re: [PATCH RFC] x86: initialize initial_page_table before paravirt jumps
Date: Mon, 13 Dec 2010 18:03:38 +1030 [thread overview]
Message-ID: <201012131803.39427.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4D011758.6010501@goop.org>
On Fri, 10 Dec 2010 04:22:24 am Jeremy Fitzhardinge wrote:
> On 12/08/2010 05:59 PM, Rusty Russell wrote:
> > As of v2.6.36-rc8-54-gb40827f, initial_page_table needs to be set up to boot.
> > My initial fix for lguest was to cut & paste in the initialization code, but
> > as it's simply byte-twiddling (which could be done at compile time if we
> > were clever enough), it seems better to do it unconditionally.
> >
> > Jeremy, Ingo does this make sense to you? Given it's rc5, I have an
> > lguest-specific patch ready as an alternative...
>
> We have already committed a Xen-specific fix for this (twice!). Your
> patch is a no-op for Xen because we never ended up using that entry path
> through head_32.S, so if it fixes things for lguest then go for it.
Hmm, I'm going to call that "Acked-by".
But given the late stage in the cycle, I'll put the lguest-only version in
now and submit this for next merge window.
Thanks!
Rusty.
prev parent reply other threads:[~2010-12-13 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 1:59 [PATCH RFC] x86: initialize initial_page_table before paravirt jumps Rusty Russell
2010-12-09 17:52 ` Jeremy Fitzhardinge
2010-12-13 7:33 ` Rusty Russell [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=201012131803.39427.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=Ian.Campbell@citrix.com \
--cc=bbpetkov@yahoo.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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