From: Xie XiuQi <xiexiuqi@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
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: Thu, 7 May 2015 14:01:45 +0800 [thread overview]
Message-ID: <554AFFC9.2040904@huawei.com> (raw)
In-Reply-To: <20150506222551.56108f53@grimm.local.home>
On 2015/5/7 10:25, Steven Rostedt wrote:
> On Mon, 20 Apr 2015 16:44:40 +0800
> Xie XiuQi <xiexiuqi@huawei.com> wrote:
>
...
>> + *
>> + * 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" ) \
>
> "Ignored" ?
My fault, I'll correct it, thanks.
>
>> + 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" ) \
...
>> + ),
>> +
>> + TP_fast_assign(
>> + __entry->pfn = pfn;
>> + __entry->type = type;
>> + __entry->result = result;
>> + ),
>> +
>> + TP_printk("pfn %#lx: recovery action for %s: %s",
>
> Hmm, "%#" is new to me. I'm not sure libtraceevent handles that.
>
> Not your problem, I need to make sure that it does, and if it does not,
> I need to fix it.
>
> I'm not even sure what %# does.
>
> Other than the typo,
>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
Thanks,
Xie XiuQi
>
> -- Steve
>
>
>> + __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]);
>> }
>
>
> .
>
--
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 6:04 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 [this message]
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=554AFFC9.2040904@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).