From: "Jan Beulich" <JBeulich@novell.com>
To: "Ingo Molnar" <mingo@elte.hu>, "David Rientjes" <rientjes@google.com>
Cc: "Tejun Heo" <tj@kernel.org>, <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: unify "numa=" command line option handling
Date: Mon, 10 Jan 2011 08:14:48 +0000 [thread overview]
Message-ID: <4D2ACE08020000780002B481@vpn.id2.novell.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101071148120.31653@chino.kir.corp.google.com>
>>> On 07.01.11 at 20:55, David Rientjes <rientjes@google.com> wrote:
> I still don't think it meets the stable kernel rules. The changelog
> explicitly states that we do not want to disable ACPI completely, so the
> only numa= command line option that would possibly be useful on 32-bit is
> numa=off in this case. If you're compiling a 32-bit kernel for a machine
> with SRAT entries that can't be parsed by the kernel, then there's still
> no explanation as to why CONFIG_NUMA=n won't fix it.
In distro kernels you have no control over the configuration, yet you
may want the kernel to boot on a particular machine.
Jan
next prev parent reply other threads:[~2011-01-10 8:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 17:02 [PATCH] x86: unify "numa=" command line option handling Jan Beulich
2011-01-06 20:36 ` David Rientjes
2011-01-07 7:51 ` Jan Beulich
2011-01-07 9:58 ` David Rientjes
2011-01-07 10:06 ` Jan Beulich
2011-01-07 12:57 ` Ingo Molnar
2011-01-07 13:32 ` Jan Beulich
2011-01-07 14:22 ` Ingo Molnar
2011-01-07 14:26 ` Jan Beulich
2011-01-07 15:12 ` Ingo Molnar
2011-01-07 19:55 ` David Rientjes
2011-01-10 8:14 ` Jan Beulich [this message]
2011-01-07 20:37 ` Tejun Heo
2011-01-07 20:33 ` Tejun Heo
2011-01-07 20:36 ` David Rientjes
2011-01-07 20:43 ` Tejun Heo
2011-01-07 20:46 ` David Rientjes
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=4D2ACE08020000780002B481@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=tj@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