linux-kernel - Re: Hardware Error Kernel Mini-Summit

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: <4BF2C55C.9060200@redhat.com>
Date:	Tue, 18 May 2010 13:50:36 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	bluesmoke-devel@...ts.sourceforge.net,
	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Ben Woodard <woodard@...hat.com>,
	Matt Domsch <Matt_Domsch@...l.com>,
	Doug Thompson <dougthompson@...ssion.com>,
	Borislav Petkov <bp@...64.org>,
	Tony Luck <tony.luck@...el.com>,
	Brent Young <brent.young@...el.com>
Subject: Re: Hardware Error Kernel Mini-Summit

Andi Kleen wrote:
> Mauro Carvalho Chehab <mchehab@...hat.com> writes:
>> There is an immediate need for error reporting on NHM-EP class
>> systems.
> 
> Just for the innocent readers who might be mislead by this:
> 
> Nehalem-EP DIMM error accounting already works fine today using
> mcelog for most cases, including RHEL5.5 (with some limits) 
> and RHEL6beta with no additional changes needed.
> 
> In RHEL6 the daemon does the accounting and the client reports the errors
> separated for each DIMM and separated in uc and ce.  In RHEL5
> the information is in a log file and can be gotten from there.
> 
> In addition the daemon supports various advanced RAS features including
> predictive bad page offlining and various threshold triggers.

Ok. It should be clear that the main target of the mini-summit is to define
how the several subsystems will integrate into a hardware-abstracted way
to report errors from kernel. So, we're looking on the next steps to improve
what we currently have, and avoid to have more than one different subsystem
trying to get the same info, eventually using the same registers, but providing
different interfaces to userspace.

-- 

Cheers,
Mauro
--
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/