From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [PATCH] xen: correct size of level2_kernel_pgt
Date: Fri, 29 Oct 2010 18:55:33 +0100 [thread overview]
Message-ID: <1288374933.8069.63.camel@localhost.localdomain> (raw)
In-Reply-To: <4CCB0836.3040200@goop.org>
On Fri, 2010-10-29 at 18:45 +0100, Jeremy Fitzhardinge wrote:
> On 10/29/2010 10:37 AM, Ian Campbell wrote:
> > On Fri, 2010-10-29 at 18:22 +0100, Jeremy Fitzhardinge wrote:
> >> On 10/29/2010 08:56 AM, Ian Campbell wrote:
> >>> sizeof(pmd_t *) is 4 bytes on PAE leading to an allocation of only
> >>> 2048 bytes. The correct size is sizeof(pmd_t) giving us a full page
> >>> allocation.
> >>>
> >>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> >>> Cc: Jeremy Fitzhardinge <jeremy@goop.org>
> >>> ---
> >>>
> >>> Applies to mainline since 2.6.36 and to xen.git 2.6.32 based trees
> >> This is just for 2.6.37?
> > 2.6.36.stable too, I think. I added stable@kernel.org to my patch header
> > but didn't "guilt refresh" so it didn't show up here.
>
> The extend_brk() stuff was all merged this merge window. I checked out
> .36 to confirm, and there's nothing there for your patch to apply to...
Ah, I was suffering the classic confusion regarding a branch from before
a release getting merged after. Thanks!
Ian.
prev parent reply other threads:[~2010-10-29 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 15:56 [PATCH] xen: correct size of level2_kernel_pgt Ian Campbell
2010-10-29 16:18 ` Jeremy Fitzhardinge
2010-10-29 17:22 ` Jeremy Fitzhardinge
2010-10-29 17:37 ` Ian Campbell
2010-10-29 17:45 ` [Xen-devel] " Jeremy Fitzhardinge
2010-10-29 17:55 ` Ian Campbell [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=1288374933.8069.63.camel@localhost.localdomain \
--to=ian.campbell@eu.citrix.com \
--cc=jeremy@goop.org \
--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