[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BF2D564.7010101@redhat.com>
Date: Tue, 18 May 2010 14:59:00 -0300
From: Mauro Carvalho Chehab <mchehab@...hat.com>
To: Joe Perches <joe@...ches.com>
CC: 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 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?
That's the original plan. It were suggested by Ingo and Thomas at LKML. Borislav
also send a more technical proposal about it.
It actually makes sense, since some sorts of errors may affect performance
(those non-fatal errors that are auto-recovered). Also, using debugfs and the
same kind of logic used by perf to filter errors seems pertinent for hardware
errors. As the actual patches were not written yet, the details on how those
things will integrate will depend on further analysis.
--
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/
Powered by blists - more mailing lists