From: Borislav Petkov <bp@amd64.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] MAINTAINERS: Add x86 RAS people
Date: Fri, 17 Jun 2011 15:50:56 +0200 [thread overview]
Message-ID: <20110617135056.GE18054@aftab> (raw)
In-Reply-To: <20110617132757.GA9659@localhost.ucw.cz>
On Fri, Jun 17, 2011 at 09:27:58AM -0400, Pavel Machek wrote:
> On Tue 2011-06-14 18:08:54, Borislav Petkov wrote:
> > Announce the new RAS infrastructure maintainers. The file patterns below
> > will change after we start the restructuring.
> >
> > Signed-off-by: Borislav Petkov <bp@amd64.org>
> > Signed-off-by: Tony Luck <tony.luck@intel.com>
> >
> > +X86 RAS INFRASTRUCTURE
> > +M: Tony Luck <tony.luck@intel.com>
>
> this would be great place to explain "ras"...
Wikipedia has a basic overview: http://en.wikipedia.org/wiki/Reliability,_Availability_and_Serviceability
Our idea is to make error collection and reporting much more easy to
configure and much easily manageable now that reliability features are
much more important on x86. You want to be able to enforce policies
from userspace like, for example, counting errors per hw device (DRAM
ECC errors per DIMM, for example) and undertake actions when thresholds
are reached, implement a much better unified error injection scheme for
testing system reliability, etc.
Another important issue is saving oops information to persistent storage
so that it can be evaluated after reboot. While this is easy to do on
servers with their nvram, we still have no solution for general purpose
laptops. hpa had a project with oopses represented with a 2d barcode but
I still haven't had a chance to look into that.
So things like that, I'm pretty sure I'm leaving something out but you
should be getting the idea...
--
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
next prev parent reply other threads:[~2011-06-17 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 16:08 [PATCH] MAINTAINERS: Add x86 RAS people Borislav Petkov
2011-06-14 21:19 ` Ingo Molnar
2011-06-15 1:25 ` [tip:x86/urgent] x86, " tip-bot for Borislav Petkov
2011-06-17 13:27 ` [PATCH] " Pavel Machek
2011-06-17 13:50 ` Borislav Petkov [this message]
2011-06-17 21:24 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110617135056.GE18054@aftab \
--to=bp@amd64.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox