From: Xie XiuQi <xiexiuqi@huawei.com>
To: n-horiguchi@ah.jp.nec.com
Cc: rostedt@goodmis.org, mingo@redhat.com, akpm@linux-foundation.org,
kirill.shutemov@linux.intel.com, koct9i@gmail.com,
hpa@linux.intel.com, hannes@cmpxchg.org, iamjoonsoo.kim@lge.com,
luto@amacapital.net, nasa4836@gmail.com,
gong.chen@linux.intel.com, bhelgaas@google.com, bp@suse.de,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, jingle.chen@huawei.com
Subject: Re: [PATCH v4 0/3] tracing: add trace event for memory-failure
Date: Wed, 29 Apr 2015 19:14:27 +0800 [thread overview]
Message-ID: <5540BD13.1010408@huawei.com> (raw)
In-Reply-To: <1429519480-11687-1-git-send-email-xiexiuqi@huawei.com>
Hi Naoya,
Could you help to review and applied this series if possible.
Thanks,
Xie XiuQi
On 2015/4/20 16:44, 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
>
> --
> 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(-)
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-04-29 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 8:44 [PATCH v4 0/3] tracing: add trace event for memory-failure Xie XiuQi
2015-04-20 8:44 ` [PATCH v4 1/3] memory-failure: export page_type and action result Xie XiuQi
2015-05-07 0:48 ` Naoya Horiguchi
2015-04-20 8:44 ` [PATCH v4 2/3] memory-failure: change type of action_result's param 3 to enum Xie XiuQi
2015-05-07 0:08 ` Naoya Horiguchi
2015-04-20 8:44 ` [PATCH v4 3/3] tracing: add trace event for memory-failure Xie XiuQi
2015-04-20 19:53 ` Steven Rostedt
2015-05-07 0:55 ` Naoya Horiguchi
2015-05-07 2:25 ` Steven Rostedt
2015-05-07 6:01 ` Xie XiuQi
2015-04-29 11:14 ` Xie XiuQi [this message]
2015-05-07 1:12 ` [PATCH v4 0/3] " Naoya Horiguchi
2015-05-07 2:17 ` Steven Rostedt
2015-05-07 5:57 ` Xie XiuQi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5540BD13.1010408@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@linux.intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jingle.chen@huawei.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=nasa4836@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).