lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 07 Jan 2011 07:51:09 +0000
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"David Rientjes" <rientjes@...gle.com>, "Tejun Heo" <tj@...nel.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>, <tglx@...utronix.de>,
	<linux-kernel@...r.kernel.org>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86: unify "numa=" command line option handling

>>> On 06.01.11 at 21:36, David Rientjes <rientjes@...gle.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ