linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Xie XiuQi <xiexiuqi@huawei.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "rostedt@goodmis.org" <rostedt@goodmis.org>,
	"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
	"mingo@redhat.com" <mingo@redhat.com>, "bp@suse.de" <bp@suse.de>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"jingle.chen@huawei.com" <jingle.chen@huawei.com>,
	"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>,
	"jim.epost@gmail.com" <jim.epost@gmail.com>
Subject: Re: [PATCH v6 0/5] tracing: add trace event for memory-failure
Date: Thu, 21 May 2015 23:28:22 +0000	[thread overview]
Message-ID: <20150521232821.GA5502@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <1432179685-11369-1-git-send-email-xiexiuqi@huawei.com>

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

      parent reply	other threads:[~2015-05-21 23:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  3:41 Xie XiuQi
2015-05-21  3:41 ` [PATCH v6 1/5] memory-failure: export page_type and action result Xie XiuQi
2015-05-21  3:41 ` [PATCH v6 2/5] memory-failure: change type of action_result's param 3 to enum Xie XiuQi
2015-05-21  3:41 ` [PATCH v6 3/5] tracing: add trace event for memory-failure Xie XiuQi
2015-05-21  3:41 ` [PATCH v6 4/5] tracing: fix build error in mm/memory-failure.c Xie XiuQi
2015-05-21  3:41 ` [PATCH v6 5/5] trace, ras: move ras_event.h under include/trace/events Xie XiuQi
2015-05-21  9:24   ` Borislav Petkov
2015-05-21 13:01     ` Steven Rostedt
2015-05-21 23:00       ` Naoya Horiguchi
2015-05-21 23:28 ` Naoya Horiguchi [this message]

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=20150521232821.GA5502@hori1.linux.bs1.fc.nec.co.jp \
    --to=n-horiguchi@ah.jp.nec.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=gong.chen@linux.intel.com \
    --cc=jim.epost@gmail.com \
    --cc=jingle.chen@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    --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