Re: [PATCH v4 3/3] tracing: add trace event for memory-failure

2015-05-06 Thread Xie XiuQi
On 2015/5/7 10:25, Steven Rostedt wrote: > On Mon, 20 Apr 2015 16:44:40 +0800 > Xie XiuQi wrote: > ... >> + * >> + * unsigned long pfn - Page Frame Number of the corrupted page >> + * int type - Page types of the corrupted page >> + * int result - Result of recovery actio

Re: [PATCH v4 3/3] tracing: add trace event for memory-failure

2015-05-06 Thread Steven Rostedt
On Mon, 20 Apr 2015 16:44:40 +0800 Xie XiuQi wrote: > --- a/include/ras/ras_event.h > +++ b/include/ras/ras_event.h > @@ -11,6 +11,7 @@ > #include > #include > #include > +#include > > /* > * MCE Extended Error Log trace event > @@ -232,6 +233,90 @@ TRACE_EVENT(aer_event, >

Re: [PATCH v4 3/3] tracing: add trace event for memory-failure

2015-05-06 Thread Naoya Horiguchi
On Mon, Apr 20, 2015 at 04:44:40PM +0800, Xie XiuQi wrote: > RAS user space tools like rasdaemon which base on trace event, could > receive mce error event, but no memory recovery result event. So, I > want to add this event to make this scenario complete. > > This patch add a event at ras group f

Re: [PATCH v4 3/3] tracing: add trace event for memory-failure

2015-04-20 Thread Steven Rostedt
On Mon, 20 Apr 2015 16:44:40 +0800 Xie XiuQi wrote: > RAS user space tools like rasdaemon which base on trace event, could > receive mce error event, but no memory recovery result event. So, I > want to add this event to make this scenario complete. > > This patch add a event at ras group for me

[PATCH v4 3/3] tracing: add trace event for memory-failure

2015-04-20 Thread Xie XiuQi
RAS user space tools like rasdaemon which base on trace event, could receive mce error event, but no memory recovery result event. So, I want to add this event to make this scenario complete. This patch add a event at ras group for memory-failure. The output like below: # tracer: nop # # entrie