From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Allow 32bit PAE guests to change their L3 entries
Date: Mon, 18 Feb 2008 15:41:09 +0100 [thread overview]
Message-ID: <200802181541.09712.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C3DF4830.1CA03%Keir.Fraser@cl.cam.ac.uk>
On Monday 18 February 2008 15:35:28 Keir Fraser wrote:
> On 18/2/08 13:57, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> >> It breaks the fast update path, and also all mod_lN_entry() functions
> >> should probably be reorganised for consistency. I'll make these changes
> >> and apply it.
> >
> > Thank you very much. But shouldn't have c/s 17061 gone into xen-staging
> > first and then into xen-unstable ?
>
> It's in both. Also now in 3.2 and 3.1 staging trees.
Thanks. I just was surprised seeing the patch in xen-unstable before in
xen-staging. Maybe your automated regression system had a kind of a "race"
window :)
Christoph
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-02-18 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 12:32 [PATCH] Allow 32bit PAE guests to change their L3 entries Christoph Egger
2008-02-18 13:44 ` Keir Fraser
2008-02-18 13:57 ` Christoph Egger
2008-02-18 14:35 ` Keir Fraser
2008-02-18 14:41 ` Christoph Egger [this message]
2008-02-18 15:03 ` Keir Fraser
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=200802181541.09712.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.