linux-kernel - Re: [RFC] amd64_edac: syndromes loading

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 28 Oct 2009 10:15:03 -0700 (PDT)
From:	Doug Thompson <norsk5@...oo.com>
To:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, x86 <x86@...nel.org>,
	Borislav Petkov <borislav.petkov@....com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] amd64_edac: syndromes loading



--- On Wed, 10/28/09, Borislav Petkov <borislav.petkov@....com> wrote:

> From: Borislav Petkov <borislav.petkov@....com>
> Subject: [RFC] amd64_edac: syndromes loading
> To: "Ingo Molnar" <mingo@...e.hu>, "Thomas Gleixner" <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, "x86" <x86@...nel.org>
> Cc: "Doug Thompson" <norsk5@...oo.com>, "LKML" <linux-kernel@...r.kernel.org>
> Date: Wednesday, October 28, 2009, 10:35 AM
> Hi,
> 
> I've been pondering how to avoid adding almost 15K of
> syndrome tables to
> the edac driver.
> 
> The syndrome tables are used for mapping a correctable ECC
> to the
> corresponding DIMM and thus pinpointing the DIMM about to
> fail. There
> are two flavors of syndromes based on the ECCs: x4 and x8.
> The x4 table
> of size 540 u16 values is already in the driver but the x8
> is much
> bigger (4864 u16) and I wouldn't want to add it statically
> into the
> driver.
> 
> Rather, I'd like to dynamically load them depending on the
> DRAM
> configuration of each node. The two attached patches do
> that using
> the request_firmware() interface. This way, the syndrome
> tables could
> be added as binary blobs in drivers/edac/ and then
> installed with
> 'make firmware_install'. This way we avoid polluting driver
> code with
> humongous u16 arrays of ECC syndromes.

Great idea. Load only when needed, based on hardware presence by triggered by probing, instead of an implicit always loaded.

Where does the syndrome table/module/firmware live in the file system? In with the amd64 module area or elsewhere?

doug t

> 
> What do you guys think, could that be an acceptable
> approach? Any
> suggestions/comments are welcome.
> 
> Thanks.
> 
> -- 
> Regards/Gruss,
> Boris.
> 
> Operating | Advanced Micro Devices GmbH
>   System  | Karl-Hammerschmidt-Str. 34, 85609
> Dornach b. München, Germany
>  Research | Geschäftsführer: Andrew Bowd, Thomas M.
> McCoy, Giuliano Meroni
>   Center  | Sitz: Dornach, Gemeinde Aschheim,
> Landkreis München
>   (OSRC)  | Registergericht München, HRB Nr.
> 43632
> 
> 
--
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/