[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150521232821.GA5502@hori1.linux.bs1.fc.nec.co.jp>
Date: Thu, 21 May 2015 23:28:22 +0000
From: Naoya Horiguchi <n-horiguchi@...jp.nec.com>
To: Xie XiuQi <xiexiuqi@...wei.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
CC: "rostedt@...dmis.org" <rostedt@...dmis.org>,
"gong.chen@...ux.intel.com" <gong.chen@...ux.intel.com>,
"mingo@...hat.com" <mingo@...hat.com>, "bp@...e.de" <bp@...e.de>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"jingle.chen@...wei.com" <jingle.chen@...wei.com>,
"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"jim.epost@...il.com" <jim.epost@...il.com>
Subject: Re: [PATCH v6 0/5] tracing: add trace event for memory-failure
On Thu, May 21, 2015 at 11:41:20AM +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 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
>
> --
> v5->v6:
> - fix a build error
> - move ras_event.h under include/trace/events
> - rebase on top of latest mainline
>
> v4->v5:
> - fix a typo
> - rebase on top of latest mainline
>
> 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.
>
> Naoya Horiguchi (1):
> trace, ras: move ras_event.h under include/trace/events
I withdraw this patch because my assumption was wrong.
> Xie XiuQi (4):
> 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
> tracing: fix build error in mm/memory-failure.c
This patchset depends on TRACE_DEFINE_ENUM patches, so base kernel version need
to be v4.1-rc1 or later. So please do the rebasing before merging this series.
Thanks,
Naoya Horiguchi--
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