All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: "David Rientjes" <rientjes@google.com>, "Tejun Heo" <tj@kernel.org>
Cc: "Ingo Molnar" <mingo@elte.hu>, <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: Fri, 07 Jan 2011 07:51:09 +0000	[thread overview]
Message-ID: <4D26D3FD020000780002AED9@vpn.id2.novell.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101061235010.30820@chino.kir.corp.google.com>

>>> On 06.01.11 at 21:36, David Rientjes <rientjes@google.com> wrote:
> On Thu, 6 Jan 2011, Jan Beulich wrote:
> 
>> In order to be able to suppress the use of SRAT tables that 32-bit
>> Linux can't deal with (possibly leading to a non-bootable system,
>> without disabling ACPI altogether), move the "numa=" option handling
>> to common code.
>> 
> 
> I like the idea in general, but I think it may collide with Tejun's NUMA 
> unification patchset for x86, which I assume will another revision once 
> the merge window for .38 closes?  Or maybe he'd like to merge your patch 
> with his series and push it as one?

I would assume that if unification is done, then the command line
option would become common too. Tejun?

However, the problem my patch addresses has been long standing
(I noted it with our .32 based kernel, but according to my looking at
the code it would go back to at least .27), so I'd like to ask for it to
be merged independently (and I should probably have copied stable
too), unless (quite unlikely) Tejun's merge is intended to also be
applied to stable kernels.

Jan


  reply	other threads:[~2011-01-07  7:51 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 [this message]
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
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=4D26D3FD020000780002AED9@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 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.