lkml.org 
[lkml]   [2010]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: perf, ftrace and MCEs

* Borislav Petkov <bp@alien8.de> wrote:

> Hi,
>
> so I finally had some spare time to stare at perf/ftrace code and ponder on
> how to use those facilities for MCE collecting and reporting. Btw, I have to
> say, it took me quite a while to understand what goes where - my suggestion
> to anyone who tries to understand how perf/ftrace works is to do make
> <file.i> where there is at least one trace_XXX emit record function call and
> start untangling code paths from there.
>
> So anyway, here are some questions I had, I just as well may've missed
> something so please correct me if I'm wrong:
>
> 1. Since machine checks can happen at any time, we need to have the MCE
> tracepoint (trace_mce_record() in <include/trace/events/mce.h>) always
> enabled. This, in turn, means that we need the ftrace/perf infrastructure
> always compiled in (lockless ring buffer, perf_event.c stuff) on any x86
> system so that MCEs can be handled at anytime. Is this going to be ok to be
> enabled on _all_ machines, hmmm... I dunno, maybe only a subset of those
> facilites at least.

Yeah - and this happens on x86 anyway so you can rely on it.

> 2. Tangential to 1., we need that "thin" software layer prepared for
> decoding and reporting them as early as possible. event_trace_init() is an
> fs_initcall and executed too late, IMHO. The ->perf_event_enable in the
> ftrace_event_call is enabled even later on the perf init path over the
> sys_perf_even_open which is at userspace time. In our case, this is going be
> executed by the error logging and decoding daemon I guess.

We could certainly move bits of this initialization earlier.

Also we could add the notion of 'persistent' events that dont have a
user-space process attached to them - and which would buffer to a certain
degree. Such persistent events could be initialized during bootup and the
daemon could pick up the events later on.

In-kernel actions/policy could work off the callback mechanism. (See for
example how the new NMI watchdog code in tip:perf/nmi makes use of it - or how
the hw-breakpoints code utilizes it.) These would work even if there's no
user-space daemon attached (or if the daemon has been stopped). So i dont see
a significant design problem here - it's all natural extensions of existing
perf facilities and could be used for other purposes as well.

> 3. Since we want to listen for MCEs all the time, the concept of enabling
> and disabling those events does not apply in the sense of performance
> profiling. [...]

Correct.

> [...] IOW, MCEs need to be able to be logged to the ring buffer at any time.
> I guess this is easily done - we simply enable MCE events at the earliest
> moment possible and disable them on shutdown; done.
>
> So yeah, some food for thought but what do you guys think?

Note that it doesnt _have to_ go to the ftrace ring-buffer. If the daemon (or
whatever facility picking up the events) keeps a global (per cpu) MCE perf
event enabled all the time then it might be doing that regardless of ftrace.

Some decoupling from ftrace could be done here easily. I'd suggest to not
worry about it - once we have the MCE event code we can certainly reshape the
underlying support code to be more readily available/configurable. (or even
built-in) This is not really a significant design issue.

To start with this, a quick initial prototype could use the 'perf trace' live
mode tracing script. (See latest -tip, 'perf trace --script <script-name>' and
'perf record -o -' to activate live mode.)

Note that there's also 'perf inject' now, which can be used to simulate rare
events and test the daemon's reactions to it. (Right now perf-inject is only
used to inject certain special build-id events, but it can be used for the
injection of MCE events as well.)

Thanks,

Ingo


\
 
 \ /
  Last update: 2010-05-04 13:35    [W:0.088 / U:3.344 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site