From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@amd64.org>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Tony Luck <tony.luck@intel.com>,
edac-devel <linux-edac@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RAS trace event proto
Date: Tue, 21 Feb 2012 09:48:18 -0500 [thread overview]
Message-ID: <1329835698.25686.60.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20120221141231.GA15515@aftab>
On Tue, 2012-02-21 at 15:12 +0100, Borislav Petkov wrote:
> > Also, folding everything into just one string prevents (or make hard) the usage of
> > the perf filters, for example, to filter only the errors at the memory controller 1.
>
> Huh, because you can't grep through the trace anymore...?
>
I believe Mauro is talking about the tracing filters used by both perf
and ftrace that lets you ignore trace events when the contents of the
event does not match the filter. This is filtering out events before
they go to the buffer.
-- Steve
next prev parent reply other threads:[~2012-02-21 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 14:59 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 [this message]
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
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=1329835698.25686.60.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=bp@amd64.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®