lkml.org 
[lkml]   [2015]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH v4 0/3] tracing: add trace event for memory-failure
Date
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 patchset add a event at ras group for memory-failure.

The output like below:
# tracer: nop
#
# entries-in-buffer/entries-written: 2/2 #P:24
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
mce-inject-13150 [001] .... 277.019359: memory_failure_event: pfn 0x19869: recovery action for free buddy page: Delayed

--
v3->v4:
- rebase on top of latest linux-next
- update comments as Naoya's suggestion
- add #ifdef CONFIG_MEMORY_FAILURE for this trace event
- change type of action_result's param 3 to enum

v2->v3:
- rebase on top of linux-next
- based on Steven Rostedt's "tracing: Add TRACE_DEFINE_ENUM() macro
to map enums to their values" patch set v1.

v1->v2:
- Comment update
- Just passing 'result' instead of 'action_name[result]',
suggested by Steve. And hard coded there because trace-cmd
and perf do not have a way to process enums.

Xie XiuQi (3):
memory-failure: export page_type and action result
memory-failure: change type of action_result's param 3 to enum
tracing: add trace event for memory-failure

include/linux/mm.h | 34 ++++++++++
include/ras/ras_event.h | 85 ++++++++++++++++++++++++
mm/memory-failure.c | 172 ++++++++++++++++++++----------------------------
3 files changed, 190 insertions(+), 101 deletions(-)

--
1.8.3.1



\
 
 \ /
  Last update: 2015-04-20 11:21    [W:0.116 / U:0.888 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site