[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1289413916.2084.30.camel@laptop>
Date: Wed, 10 Nov 2010 19:31:56 +0100
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...e.hu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Huang, Ying" <ying.huang@...el.com>,
"bp@...en8.de" <bp@...en8.de>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mchehab@...hat.com" <mchehab@...hat.com>,
Frédéric Weisbecker <fweisbec@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Arjan van de Ven <arjan@...radead.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: RE: [RFC/Requirements/Design] h/w error reporting
On Wed, 2010-11-10 at 10:23 -0800, Luck, Tony wrote:
> > A few of things that pop up quickly are:
> >
> > 1) lockless
>
> This is a clear requirement for use in h/w error
> reporting too. Taking locks in NMI or machine
> check handler isn't an option.
Don't worry, lots of PMIs are NMIs, perf needs to be fully NMI safe
otherwise things simply don't work.
--
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