From: Jon Tollefson <kniht@linux.vnet.ibm.com>
To: stable@kernel.org
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: 16G related patches for stable kernel 2.6.27
Date: Wed, 29 Oct 2008 15:56:56 -0500 [thread overview]
Message-ID: <4908CE18.3030205@linux.vnet.ibm.com> (raw)
Please consider the following patches for the 2.6.27 stable tree.
The first two allow a powerpc machine with more then 2 numa nodes
to boot when 16G pages are enabled. The third one allows a powerpc
machine to boot if using 16G pages and the mem= boot param.
thanks,
Jon
powerpc: Reserve in bootmem lmb reserved regions that cross NUMA nodes
commit 8f64e1f2d1e09267ac926e15090fd505c1c0cbcb
powerpc/numa: Make memory reserve code more robust
commit e81703724a966120ace6504c993bda9e084cbf3e
powerpc: Don't use a 16G page if beyond mem= limits
commit 4792adbac9eb41cea77a45ab76258ea10d411173
next reply other threads:[~2008-10-29 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 20:56 Jon Tollefson [this message]
2008-11-04 22:07 ` [stable] 16G related patches for stable kernel 2.6.27 Greg KH
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=4908CE18.3030205@linux.vnet.ibm.com \
--to=kniht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).