linux-kernel - Re: linux-next: manual merge of the char-misc tree with the ia64 tree

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] [day] [month] [year] [list]

Date:	Tue, 15 Jul 2014 18:18:02 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
	Arnd Bergmann <arnd@...db.de>,
	"Chen, Gong" <gong.chen@...ux.intel.com>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andreas Noever <andreas.noever@...il.com>
Subject: Re: linux-next: manual merge of the char-misc tree with the ia64 tree

On Tue, Jul 15, 2014 at 03:57:42PM +0000, Luck, Tony wrote:
> Oops - not quite. We moved creation of the EDAC trace point into
> drivers/ras/ras.c and edac is not x86 specific.
>
> We also create the PCIe AER tracepoint there too - PCIe is not x86
> specific.

Right, but AFAIK, only x86 uses those. And frankly, we don't know
whether other arches would have interest in those or would like to grow
their own.

So, I don't have an idea whether we want to make the whole RAS stuff
arch-specific or we have to talk about it or we have to leave us that
option open and so on...

It is hard to say.

One example to mud the situation even more :-):

The APEI stuff is apparently being used by arm now too, but without the
NMI which is x86-specific. Carving that whole thing out took a bit of
work but it got done.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/