From: Andi Kleen <ak@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86: fix PSE pagetable construction
Date: Sat, 28 Apr 2007 20:03:29 +0200 [thread overview]
Message-ID: <200704282003.30118.ak@suse.de> (raw)
In-Reply-To: <m1r6q4e7kk.fsf@ebiederm.dsl.xmission.com>
On Saturday 28 April 2007 19:23:55 Eric W. Biederman wrote:
> Andi Kleen <ak@suse.de> writes:
>
> >> My preference would be for whoever had:
> >> paravirt_ops-hooks-to-set-up-initial-pagetable.patch
> >
> > That would be very messy because there are many followup dependencies.
> >
> > But once we have a good fix aggreed by everybody I can merge it into the
> > initial patch then.
>
> I don't see Xen patches merged yet in your tree yet.
Hmm, I thought you were talking about paravirt-initial-pagetable ?
That one is in my tree already. The Xen patches that are still outstanding
iirc are all addons patches, as they don't impact existing code paths anymore.
-Andi
next prev parent reply other threads:[~2007-04-28 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 2:15 [PATCH] x86: fix PSE pagetable construction Jeremy Fitzhardinge
2007-04-28 5:56 ` Eric W. Biederman
2007-04-28 6:30 ` Jeremy Fitzhardinge
2007-04-28 6:39 ` Eric W. Biederman
2007-04-28 10:29 ` Andi Kleen
2007-04-28 14:28 ` Jeremy Fitzhardinge
2007-04-28 15:27 ` Eric W. Biederman
2007-04-28 23:25 ` Jeremy Fitzhardinge
2007-04-28 17:23 ` Eric W. Biederman
2007-04-28 18:03 ` Andi Kleen [this message]
2007-04-28 18:32 ` Eric W. Biederman
2007-04-28 10:25 ` Andi Kleen
2007-04-28 14:30 ` Jeremy Fitzhardinge
2007-04-28 14:55 ` Jeremy Fitzhardinge
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=200704282003.30118.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.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