[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A258C2@ORSMSX114.amr.corp.intel.com>
Date: Fri, 20 Mar 2015 17:24:21 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Xie XiuQi <xiexiuqi@...wei.com>, Borislav Petkov <bp@...e.de>
CC: "n-horiguchi@...jp.nec.com" <n-horiguchi@...jp.nec.com>,
"gong.chen@...ux.intel.com" <gong.chen@...ux.intel.com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"jingle.chen@...wei.com" <jingle.chen@...wei.com>
Subject: RE: [PATCH] tracing: add trace event for memory-failure
> 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?
-Tony
Powered by blists - more mailing lists