Messages in this thread | | | Date | Tue, 11 May 2010 17:37:57 +0200 | From | Borislav Petkov <> | Subject | Re: [RFC][PATCH 3/9] perf: export registerred pmus via sysfs |
| |
From: Peter Zijlstra <peterz@infradead.org> Date: Tue, May 11, 2010 at 10:25:15AM -0400
> On Tue, 2010-05-11 at 16:15 +0200, Borislav Petkov wrote: > > Another point I have is that MCEs don't need pmus so we should consider > > having the ability to decouple events from pmus. > > Strictly speaking tracepoints are software events, which run off of a > software 'pmu'. So no, we can't decouple, they need a 'pmu' context.
We could make this configurable depending on the severity of the error. I'm guessing for further event handling through the perf infrastructure we cannot run without a sw pmu context but on critical conditions we need to run as fast and as sparingly as possible so I'm thinking maybe adding some specially tailored callbacks to the MCE tracepoint trace_mce_record, as Steven suggested.
> > What you basically want to have is a tracepoint which is "persistent," > > as Ingo suggested earlier, and it buffers MCEs occurring at any time > > into a ring buffer until a userspace daemon or similar sucks that data > > out for processing (critical stuff is handled differently, of course). > > And this should work on any x86 hw supporting MCA without hw perf > > monitoring features. > > Try building x86 without perf hw support :/
I dunno, maybe decoupling wouldn't be necessary per se but I was simply pointing out that MCEs shouldn't necessarily depend on the presence on hardware performance counters.
-- Regards/Gruss, Boris.
-- Advanced Micro Devices, Inc. Operating Systems Research Center
| |