[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110803171608.GA16116@gere.osrc.amd.com>
Date: Wed, 3 Aug 2011 19:16:08 +0200
From: Borislav Petkov <bp@...64.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: Kay Sievers <kay.sievers@...y.org>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Greg KH <greg@...ah.com>,
Nao Nishijima <nao.nishijima.xt@...achi.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
jcm@...hat.com, dle-develop@...ts.sourceforge.net,
yrl.pp-manager.tt@...achi.com, dgilbert@...erlog.com,
stefanr@...6.in-berlin.de, hare@...e.de,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>,
Tony Luck <tony.luck@...el.com>
Subject: Re: [RFC PATCH 0/4] Persistent device name using alias name
On Sat, Jul 09, 2011 at 03:11:45PM +0900, Masami Hiramatsu wrote:
> BTW, I'm also interested in that structured error events, from the long
> term view and viewpoint of tracers :)
Let me chime in a "mee too" from the HW errors perspective.
> I think we could expand current TRACE_EVENT macro to define those
> error events.
Concerning structure, we can use the format file in debugfs which
currently describes the fields of a tracepoint:
/sys/kernel/debug/tracing/events/../../format
and expand those to generic kernel events. Userspace parses the format
and knows exactly at what data it is looking at. Also, the idea is to
move that events hierarchy into sysfs so it will be present on every
system.
Hmm...
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists