[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100518185305.GA23921@elte.hu>
Date: Tue, 18 May 2010 20:53:05 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Joe Perches <joe@...ches.com>
Cc: Mauro Carvalho Chehab <mchehab@...hat.com>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
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
* Joe Perches <joe@...ches.com> wrote:
> On Tue, 2010-05-18 at 13:44 -0300, Mauro Carvalho Chehab wrote:
> > IMO, the first
> > step is to provide an error core integrated to perf, and then start
> > integrating the several error systems around it.
>
> Why integrated to perf?
It makes sense to use the kernel's performance events
logging framework when we are logging events about how the
system performs.
Furthermore it's NMI safe, offers structured logging, has
various streaming, multiplexing and filtering capabilities
that come handy for RAS purposes and more.
The other option would be to use an ad-hoc logging
implementation, only used for EDAC/RAS, which couldnt be
mixed with other system events. That approach has various
obvious disadvanteges so we are aiming for a unified
approach.
Thanks,
Ingo
--
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/
Powered by blists - more mailing lists