linux-kernel - Re: [PATCH 2/9] x86, RAS: Start reorganizing RAS features support

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]

Message-ID: <20111019181141.GA6346@aftab>
Date:	Wed, 19 Oct 2011 20:11:41 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>
Cc:	"Luck, Tony" <tony.luck@...el.com>, Borislav Petkov <bp@...64.org>,
	EDAC devel <linux-edac@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>, X86-ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/9] x86, RAS: Start reorganizing RAS features support

On Wed, Oct 19, 2011 at 01:22:27PM -0400, Mauro Carvalho Chehab wrote:
> Em 19-10-2011 15:13, Luck, Tony escreveu:
> >> Start relocating RAS features into a centralized location under
> >> arch/x86/kernel/cpu/ras/. Readjust Kconfig items and makefiles
> >> accordingly.
> > 
> > Not all ras features are "cpu" orientated ... should we really be
> > moving to "arch/x86/kernel/ras"?
> 
> I think that it makes sense to move MCA bits into arch/x86, but I agree
> with Tony: generally speaking, RAS is not even x86 specific.

But we are :-)

> It seems to make more sense to rename drivers/edac to drivers/ras and put
> the RAS menu there, even if the actual support for the AMD and Intel MCA
> RAS stuff is kept inside arch/x86/...

drivers/edac/ contains other architectures too, patches for which we
cannot (and probably don't want to) test so the whole deal has to be
x86-centric.

I don't consider MCE decoding and injection drivers but rather MCA
functionality extensions or something, so those should go to arch/x86/
IMHO.

And the DRAM error decoding things, aka EDAC, should stay where they
are, although I cannot call them real drivers, either. We can't move
them yet anyway because they use the whole EDAC infrastructure.

Hmm...

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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/