From: Xie XiuQi <xiexiuqi@huawei.com>
To: "Luck, Tony" <tony.luck@intel.com>, Borislav Petkov <bp@suse.de>
Cc: "n-horiguchi@ah.jp.nec.com" <n-horiguchi@ah.jp.nec.com>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"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] tracing: add trace event for memory-failure
Date: Sat, 21 Mar 2015 13:44:42 +0800 [thread overview]
Message-ID: <550D054A.9070808@huawei.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32A258C2@ORSMSX114.amr.corp.intel.com>
On 2015/3/21 1:24, Luck, Tony 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.
>
> Excellent answer. Are you going to write that patch for rasdaemon?
Yes, I will ;-)
>
> -Tony
>
--
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-03-21 5:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 3:04 Xie XiuQi
2015-03-19 3:22 ` Steven Rostedt
2015-03-19 10:39 ` Borislav Petkov
2015-03-20 4:15 ` Xie XiuQi
2015-03-20 17:24 ` Luck, Tony
2015-03-21 5:44 ` Xie XiuQi [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-13 10:10 Xie XiuQi
2015-03-13 16:37 ` Tony Luck
2015-03-13 19:32 ` Steven Rostedt
2015-03-17 10:47 ` Xie XiuQi
2015-03-18 0:55 ` Steven Rostedt
2015-03-16 9:27 ` Naoya Horiguchi
2015-03-16 13:04 ` 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=550D054A.9070808@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=bhelgaas@google.com \
--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=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