public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	Tom Zanussi <tzanussi@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] tracing/filters: remove error messages
Date: Thu, 18 Jun 2009 09:17:00 +0800	[thread overview]
Message-ID: <4A39958C.4010801@cn.fujitsu.com> (raw)
In-Reply-To: <20090617120216.GB6064@nowhere>

Frederic Weisbecker wrote:
> On Wed, Jun 17, 2009 at 04:47:15PM +0800, Li Zefan wrote:
>> Now we restore original filter is the new one can't be applied,
>> and no long show error messages, so we can remove them totally.
> 
> Why?
> These messages are very powerful to point a user to its mistakes
> in filters syntaxes or semantics.
> 
> I really think we are removing a very useful feature in this patch.
> 

I think it's better done by providing a user-space program/script.

So what's the criterion to decide what should be in kernel and
what should be in user-space?

btw, this feature is not full-fledged, that it can't point to the
exact position where error occured, and the implementation will add
complexity and I'm sure it's worthy or not.

> May be we can keep the previous filter in case of new filter string
> inserting failure, though if the user wanted to insert a new one, there
> are few chances that the previous one is still relevant for him.
> I don't know.
> 
>> Another reason is, I don't think it's good to show error messages
>> when reading a control file.
> 
> So, why not create a filter_error file in this case? One for each
> event and subsys that would print the last error?
> 

Yeah, if we do want to keep this feature in the kernel.

  reply	other threads:[~2009-06-18  1:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  8:46 [PATCH 1/2] tracing/filters: restore orignal filter when new filter isn't applicable Li Zefan
2009-06-17  8:47 ` [PATCH 2/2] tracing/filters: remove error messages Li Zefan
2009-06-17 12:02   ` Frederic Weisbecker
2009-06-18  1:17     ` Li Zefan [this message]
2009-06-18  6:10       ` Tom Zanussi
2009-06-19  5:03         ` Li Zefan
2009-06-18  5:58 ` [PATCH 1/2] tracing/filters: restore orignal filter when new filter isn't applicable Tom Zanussi
2009-06-18 23:18   ` Steven Rostedt
2009-06-19  4:46     ` Tom Zanussi
2009-06-19  5:02       ` 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=4A39958C.4010801@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tzanussi@gmail.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