linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Xie XiuQi <xiexiuqi@huawei.com>
Cc: n-horiguchi@ah.jp.nec.com, 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 3/3] tracing: add trace event for memory-failure
Date: Mon, 20 Apr 2015 15:53:48 -0400	[thread overview]
Message-ID: <20150420155348.71ab777c@gandalf.local.home> (raw)
In-Reply-To: <1429519480-11687-4-git-send-email-xiexiuqi@huawei.com>

On Mon, 20 Apr 2015 16:44:40 +0800
Xie XiuQi <xiexiuqi@huawei.com> 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 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
> 
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Xie XiuQi <xiexiuqi@huawei.com>

Looks good to me.

Acked-by: Steven Rostedt <rostedt@goodmis.org>

-- Steve

--
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>

  reply	other threads:[~2015-04-20 19:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  8:44 [PATCH v4 0/3] " 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 [this message]
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 ` [PATCH v4 0/3] " Xie XiuQi
2015-05-07  1:12   ` 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=20150420155348.71ab777c@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --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=tony.luck@intel.com \
    --cc=xiexiuqi@huawei.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