From: Tom Zanussi <tzanussi@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tracing/filters: Improve subsystem filter
Date: Tue, 21 Jul 2009 00:56:36 -0500 [thread overview]
Message-ID: <1248155796.6323.46.camel@tropicana> (raw)
In-Reply-To: <4A651DF2.3060403@cn.fujitsu.com>
On Tue, 2009-07-21 at 09:46 +0800, Li Zefan wrote:
> >> Proposal 2:
> >>
> >> # cat filter
> >> irq_handler_entry: irq == 5
> >> irq_handler_exit: none
> >> softirq_entry: vec == 1
> >> softirq_exit: vec == 2
> >
> > I like proposal 2, it is very intuitive.
> >
>
> Me too.
Me three. It's nice to see all the filters for the subsystem in one
place without having to descend into the event subdirs. It might also
be nice to see which events are enabled by looking at the subsystem
'enable' file too. Or maybe the subsystem filter file should show only
filters for enabled events...
>
> >> Which do you think is better? Or do you have some better idea?
> >>
> >> And in the failure case:
> >>
> >> # echo 'irq == not_num' > filter
> >> bash: echo: write error: Invalid argument
> >>
> >> 1:
> >> # cat filter
> >> (still shows filters in each event like above)
> >>
> >> or shows error message (the current behavior)
> >
> > No need to show error messages of failed filter modifications in the
> > "filter" file.
> >
> >> 2:
> >> # cat filter
> >> irq == not_num
> >> ^
> >> parse_error: Couldn't find or set field in one of a subsystem's events
> >
> > This looks good, BUT, it is too much. If you want to implement an error
> > message like the above, it should probably be a "pr_info()" thing.
> >
>
> Yeah, I think it's too much too, but that's exactly what we have.
> And I posted a patch to remove those error messages, but Tom and
> Frederic didn't seem to like it:
>
> http://lkml.org/lkml/2009/6/17/89
It made sense to me to overload the filter file for individual events
this way since error messages (which I still think are useful) and valid
filters are mutually exclusive. But that's not the case for the
subsystem filter files, so for those maybe a filter_error file makes
sense. Maybe for consistency, it also makes sense for the individual
events too - I don't really have a strong opinion either way.
Tom
next prev parent reply other threads:[~2009-07-21 5:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 2:20 Li Zefan
2009-07-20 16:08 ` Steven Rostedt
2009-07-20 16:16 ` Frederic Weisbecker
2009-07-20 16:35 ` Steven Rostedt
2009-07-21 1:25 ` Li Zefan
2009-07-21 1:35 ` Steven Rostedt
2009-07-21 1:46 ` Li Zefan
2009-07-21 2:14 ` Steven Rostedt
2009-07-21 5:56 ` Tom Zanussi [this message]
2009-07-21 5:36 ` Tom Zanussi
2009-07-21 6:35 ` Li Zefan
2009-07-21 7:22 ` Tom Zanussi
2009-08-05 8:19 ` [tip:tracing/core] tracing/filters: improve " tip-bot for Li Zefan
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=1248155796.6323.46.camel@tropicana \
--to=tzanussi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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®