From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Borislav Petkov <bp@amd64.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
edac-devel <linux-edac@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RAS trace event proto
Date: Wed, 22 Feb 2012 12:25:03 -0200 [thread overview]
Message-ID: <4F44FABF.1020401@redhat.com> (raw)
In-Reply-To: <20120222140526.GE26845@aftab>
Em 22-02-2012 12:05, Borislav Petkov escreveu:
> On Wed, Feb 22, 2012 at 11:32:16AM -0200, Mauro Carvalho Chehab wrote:
>
>> So, in other words, I think that the _best_ way to represent an MCA
>> type of error is to use an event with the following prototype:
>
> No, it's not.
Why? It fits with all existing edac drivers, and it seems to fit with
mce_amd, based on the examples you gave.
>
> And if you're going to repeat yourself for the 100th time as to why,
> don't even bother replying.
Well, a single string is not ok, as it is not easily parseable and it
doesn't allow to use the perf filters.
We need to agree on some trace format that fits, and that covers the
needs by the existing drivers.
I'm ok, if you didn't like the format I've proposed, if you have
a better proposal.
Regards,
Mauro.
next prev parent reply other threads:[~2012-02-22 14:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 14:59 RAS trace event proto Borislav Petkov
2012-02-21 1:14 ` Steven Rostedt
2012-02-21 10:15 ` Borislav Petkov
2012-02-21 12:24 ` Mauro Carvalho Chehab
2012-02-21 14:12 ` Borislav Petkov
2012-02-21 14:48 ` Steven Rostedt
2012-02-21 14:59 ` Borislav Petkov
2012-02-21 16:18 ` Mauro Carvalho Chehab
2012-02-22 0:58 ` Luck, Tony
2012-02-22 10:43 ` Borislav Petkov
2012-02-22 12:02 ` Mauro Carvalho Chehab
2012-02-22 12:25 ` Borislav Petkov
2012-02-22 13:32 ` Mauro Carvalho Chehab
2012-02-22 14:05 ` Borislav Petkov
2012-02-22 14:25 ` Mauro Carvalho Chehab [this message]
2012-02-22 14:26 ` Steven Rostedt
2012-02-22 15:59 ` Borislav Petkov
2012-02-27 15:54 ` Borislav Petkov
2012-02-21 17:28 ` Mauro Carvalho Chehab
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=4F44FABF.1020401@redhat.com \
--to=mchehab@redhat.com \
--cc=bp@amd64.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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