mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Changbin Du <changbin.du@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Changbin Du <changbin.du@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] perf: support multiple debug options separated by ','
Date: Tue, 26 Nov 2019 22:34:04 +0800	[thread overview]
Message-ID: <20191126143402.yxb2djhlpm5tuahf@mail.google.com> (raw)
In-Reply-To: <20191126094508.GB32367@krava>

On Tue, Nov 26, 2019 at 10:45:08AM +0100, Jiri Olsa wrote:
> On Mon, Nov 25, 2019 at 11:14:45PM +0800, Changbin Du wrote:
> > This patch adds support for multiple debug options separated by ',' and
> > non-int values.
> > 	--debug verbose=2,stderr
> > 
> > Signed-off-by: Changbin Du <changbin.du@gmail.com>
> > ---
> >  tools/perf/Documentation/perf.txt | 13 +++--
> >  tools/perf/util/debug.c           | 89 ++++++++++++++++---------------
> >  2 files changed, 53 insertions(+), 49 deletions(-)
> > 
> > diff --git a/tools/perf/Documentation/perf.txt b/tools/perf/Documentation/perf.txt
> > index 3f37ded13f8c..fd8d790f68a7 100644
> > --- a/tools/perf/Documentation/perf.txt
> > +++ b/tools/perf/Documentation/perf.txt
> > @@ -19,13 +19,12 @@ OPTIONS
> >  	  --debug verbose=2 # sets verbose = 2
> >  
> >  	List of debug variables allowed to set:
> > -	  verbose          - general debug messages
> > -	  ordered-events   - ordered events object debug messages
> > -	  data-convert     - data convert command debug messages
> > -	  stderr           - write debug output (option -v) to stderr
> > -	                     in browser mode
> > -	  perf-event-open  - Print perf_event_open() arguments and
> > -			     return value
> > +	  verbose=level		- general debug messages
> > +	  ordered-events=level	- ordered events object debug messages
> > +	  data-convert=level	- data convert command debug messages
> > +	  stderr		- write debug output (option -v) to stderr
> > +	  perf-event-open	- Print perf_event_open() arguments and
> > +	                          return value in browser mode
> 
> it's just the list and the doc says user can use values
> there, so no need for the '=level' there
> 
> also we allow this:
>   perf --debug stderr=9 record ls
> 
> so I thinks we should keep it general in documentation,
> eventhough it will always mean just stderr=true for any
> value
>
I changed them as below. For stderr and perf_event_open, the value is ignored
even it is given.

--debug::
	Setup debug variable (see list below). The range of 'level' value
	is (0, 10). Use like:
	  --debug verbose   # sets verbose = 1
	  --debug verbose=2,file=~/perf.log
	                    # sets verbose = 2 and save log to file

	List of debug variables allowed to set:
	  verbose[=level]	- general debug messages
	  ordered-events[=level]- ordered events object debug messages
	  data-convert[=level]	- data convert command debug messages
	  stderr		- write debug output (option -v) to stderr
	                          in browser mode
	  perf-event-open	- Print perf_event_open() arguments and
	                          return value

> jirka
> 

-- 
Cheers,
Changbin Du

  reply	other threads:[~2019-11-26 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 15:14 [PATCH v6 0/2] perf: add support for logging debug messages to file Changbin Du
2019-11-25 15:14 ` [PATCH v6 1/2] perf: support multiple debug options separated by ',' Changbin Du
2019-11-26  5:40   ` Ravi Bangoria
2019-11-26 14:18     ` Changbin Du
2019-11-26  9:45   ` Jiri Olsa
2019-11-26 14:34     ` Changbin Du [this message]
2019-11-25 15:14 ` [PATCH v6 2/2] perf: add support for logging debug messages to file Changbin Du
2019-11-26  9:50   ` Jiri Olsa

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=20191126143402.yxb2djhlpm5tuahf@mail.google.com \
    --to=changbin.du@gmail.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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®