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, gong.chen@linux.intel.com, bp@suse.de,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, jingle.chen@huawei.com
Subject: Re: [PATCH v5 3/3] tracing: add trace event for memory-failure
Date: Fri, 8 May 2015 09:00:02 +0800 [thread overview]
Message-ID: <554C0A92.2080709@huawei.com> (raw)
In-Reply-To: <20150507090127.34a7f93f@gandalf.local.home>
On 2015/5/7 21:01, Steven Rostedt wrote:
> On Thu, 7 May 2015 19:38:01 +0800
> Xie XiuQi <xiexiuqi@huawei.com> wrote:
>
>> + TP_printk("pfn %#lx: recovery action for %s: %s",
>
> I checked the libtraceevent code, and %# is handled.
Good, thank you!
>
> -- 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 */
>>
>
> .
>
--
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>
prev parent reply other threads:[~2015-05-08 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 11:37 [PATCH v5 0/3] tracing: add trace event for memory-failure Xie XiuQi
2015-05-07 11:37 ` [PATCH v5 1/3] memory-failure: export page_type and action result Xie XiuQi
2015-05-07 11:38 ` [PATCH v5 2/3] memory-failure: change type of action_result's param 3 to enum Xie XiuQi
2015-05-07 11:38 ` [PATCH v5 3/3] tracing: add trace event for memory-failure Xie XiuQi
2015-05-07 13:01 ` Steven Rostedt
2015-05-08 1:00 ` Xie XiuQi [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=554C0A92.2080709@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=jingle.chen@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=n-horiguchi@ah.jp.nec.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).