From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Xie XiuQi <xiexiuqi@huawei.com>
Cc: "rostedt@goodmis.org" <rostedt@goodmis.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"koct9i@gmail.com" <koct9i@gmail.com>,
"hpa@linux.intel.com" <hpa@linux.intel.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
"luto@amacapital.net" <luto@amacapital.net>,
"nasa4836@gmail.com" <nasa4836@gmail.com>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
"bhelgaas@google.com" <bhelgaas@google.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>
Subject: Re: [PATCH v4 3/3] tracing: add trace event for memory-failure
Date: Thu, 7 May 2015 00:55:11 +0000 [thread overview]
Message-ID: <20150507005510.GB7745@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <1429519480-11687-4-git-send-email-xiexiuqi@huawei.com>
On Mon, Apr 20, 2015 at 04:44:40PM +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 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>
Reviewed-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> ---
> include/ras/ras_event.h | 85 +++++++++++++++++++++++++++++++++++++++++++++++++
> mm/memory-failure.c | 3 ++
> 2 files changed, 88 insertions(+)
>
> diff --git a/include/ras/ras_event.h b/include/ras/ras_event.h
> index 79abb9c..258ed89 100644
> --- a/include/ras/ras_event.h
> +++ b/include/ras/ras_event.h
> @@ -11,6 +11,7 @@
> #include <linux/pci.h>
> #include <linux/aer.h>
> #include <linux/cper.h>
> +#include <linux/mm.h>
>
> /*
> * MCE Extended Error Log trace event
> @@ -232,6 +233,90 @@ TRACE_EVENT(aer_event,
> __print_flags(__entry->status, "|", aer_uncorrectable_errors))
> );
>
> +/*
> + * memory-failure recovery action result event
> + *
> + * unsigned long pfn - Page Frame Number of the corrupted page
> + * int type - Page types of the corrupted page
> + * int result - Result of recovery action
> + */
> +
> +#ifdef CONFIG_MEMORY_FAILURE
> +#define MF_ACTION_RESULT \
> + EM ( MF_IGNORED, "Ignord" ) \
> + EM ( MF_FAILED, "Failed" ) \
> + EM ( MF_DELAYED, "Delayed" ) \
> + EMe ( MF_RECOVERED, "Recovered" )
> +
> +#define MF_PAGE_TYPE \
> + EM ( MF_MSG_KERNEL, "reserved kernel page" ) \
> + EM ( MF_MSG_KERNEL_HIGH_ORDER, "high-order kernel page" ) \
> + EM ( MF_MSG_SLAB, "kernel slab page" ) \
> + EM ( MF_MSG_DIFFERENT_COMPOUND, "different compound page after locking" ) \
> + EM ( MF_MSG_POISONED_HUGE, "huge page already hardware poisoned" ) \
> + EM ( MF_MSG_HUGE, "huge page" ) \
> + EM ( MF_MSG_FREE_HUGE, "free huge page" ) \
> + EM ( MF_MSG_UNMAP_FAILED, "unmapping failed page" ) \
> + EM ( MF_MSG_DIRTY_SWAPCACHE, "dirty swapcache page" ) \
> + EM ( MF_MSG_CLEAN_SWAPCACHE, "clean swapcache page" ) \
> + EM ( MF_MSG_DIRTY_MLOCKED_LRU, "dirty mlocked LRU page" ) \
> + EM ( MF_MSG_CLEAN_MLOCKED_LRU, "clean mlocked LRU page" ) \
> + EM ( MF_MSG_DIRTY_UNEVICTABLE_LRU, "dirty unevictable LRU page" ) \
> + EM ( MF_MSG_CLEAN_UNEVICTABLE_LRU, "clean unevictable LRU page" ) \
> + EM ( MF_MSG_DIRTY_LRU, "dirty LRU page" ) \
> + EM ( MF_MSG_CLEAN_LRU, "clean LRU page" ) \
> + EM ( MF_MSG_TRUNCATED_LRU, "already truncated LRU page" ) \
> + EM ( MF_MSG_BUDDY, "free buddy page" ) \
> + EM ( MF_MSG_BUDDY_2ND, "free buddy page (2nd try)" ) \
> + EMe ( MF_MSG_UNKNOWN, "unknown page" )
> +
> +/*
> + * First define the enums in MM_ACTION_RESULT to be exported to userspace
> + * via TRACE_DEFINE_ENUM().
> + */
> +#undef EM
> +#undef EMe
> +#define EM(a,b) TRACE_DEFINE_ENUM(a);
> +#define EMe(a,b) TRACE_DEFINE_ENUM(a);
> +
> +MF_ACTION_RESULT
> +MF_PAGE_TYPE
> +
> +/*
> + * Now redefine the EM() and EMe() macros to map the enums to the strings
> + * that will be printed in the output.
> + */
> +#undef EM
> +#undef EMe
> +#define EM(a,b) { a, b },
> +#define EMe(a,b) { a, b }
> +
> +TRACE_EVENT(memory_failure_event,
> + TP_PROTO(unsigned long pfn,
> + int type,
> + int result),
> +
> + TP_ARGS(pfn, type, result),
> +
> + TP_STRUCT__entry(
> + __field(unsigned long, pfn)
> + __field(int, type)
> + __field(int, result)
> + ),
> +
> + TP_fast_assign(
> + __entry->pfn = pfn;
> + __entry->type = type;
> + __entry->result = result;
> + ),
> +
> + TP_printk("pfn %#lx: recovery action for %s: %s",
> + __entry->pfn,
> + __print_symbolic(__entry->type, MF_PAGE_TYPE),
> + __print_symbolic(__entry->result, MF_ACTION_RESULT)
> + )
> +);
> +#endif /* CONFIG_MEMORY_FAILURE */
> #endif /* _TRACE_HW_EVENT_MC_H */
>
> /* This part must be outside protection */
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index f074f8e..42c5981 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -56,6 +56,7 @@
> #include <linux/mm_inline.h>
> #include <linux/kfifo.h>
> #include "internal.h"
> +#include "ras/ras_event.h"
>
> int sysctl_memory_failure_early_kill __read_mostly = 0;
>
> @@ -850,6 +851,8 @@ static struct page_state {
> static void action_result(unsigned long pfn, enum mf_action_page_type type,
> enum mf_result result)
> {
> + trace_memory_failure_event(pfn, type, result);
> +
> pr_err("MCE %#lx: recovery action for %s: %s\n",
> pfn, action_page_types[type], action_name[result]);
> }
> --
> 1.8.3.1
>
--
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-05-07 1:13 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
2015-05-07 0:55 ` Naoya Horiguchi [this message]
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=20150507005510.GB7745@hori1.linux.bs1.fc.nec.co.jp \
--to=n-horiguchi@ah.jp.nec.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=nasa4836@gmail.com \
--cc=rostedt@goodmis.org \
--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