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:	Thu, 27 Oct 2011 13:38:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steffen Persvold <sp@...ascale.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	Daniel J Blueman <daniel@...ascale-asia.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, H Peter Anvin <hpa@...or.com>,
	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH 2/3] Add multi-node boot support


* Steffen Persvold <sp@...ascale.com> wrote:

> > If it's absolutely needed then add a proper quirk handler instead 
> > of polluting the generic code.
> 
> We wanted to reuse as much of the generic AMD code as possible, but 
> it's tricky because most of that code is based around a single HT 
> fabric design, whereas a NumaChip based systems consists of several 
> HT fabrics connected together thus you will have identical 
> NorthBridge IDs (0-7) etc. shared between all systems.
> 
> How would you suggest we add a quirk handler for it ?

So what we want on NumaChip systems is for the node ID in the BIOS 
SRAT table to override the node ID that is read from the hardware, 
right?

Instead of making it a is_numachip_system() thing it would be better 
to detect that the two do not match, and override it if the platform 
says that we should override it - and warn about the mismatch 
otherwise.

Whether to override could be a new srat_override() function in the 
x86_init structure or so.

Thomas, Peter, what do you think?

Thanks,

	Ingo
--
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