From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 4/4] perf tools: Add --debug optionto set debug variable
Date: Mon, 14 Jul 2014 16:51:30 +0200 [thread overview]
Message-ID: <20140714145130.GG17761@krava.redhat.com> (raw)
In-Reply-To: <87egxo2xat.fsf@sejong.aot.lge.com>
On Mon, Jul 14, 2014 at 04:51:06PM +0900, Namhyung Kim wrote:
> Hi Jiri,
>
> On Sat, 12 Jul 2014 23:56:28 +0200, Jiri Olsa wrote:
> > Adding --debug option as a way to setup debug variables.
> > Starting with support for verbose, more will come.
> >
> > It's possible to use it now with report command:
> > $ perf report --debug verbose
> > $ perf report --debug verbose=2
> >
> > I'll need this support to add separated debug variable
> > for ordered events change in order to separate debug
> > output out of standard verbose stream.
>
> Hmm.. okay. I think there'll be more users for this.
>
>
> >
> > Also removing unneeded getopt.h includes.
>
> I guess Arnaldo wants to see it as a separate change ;-)
maybe ;-) I hit an issue with this by adding #include "parse-options.h"
into debug.h ... we have a some name clashes with getopt.h
>
>
> > +static struct variables_t {
> > + const char *name;
> > + int *ptr;
> > +} variables[] = {
>
> This is a too general name. How about debug_variable or debug_domain?
debug_variable sounds good to me, will change
thanks,
jirka
prev parent reply other threads:[~2014-07-14 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 21:56 [PATCH 0/4] perf tools: Add support for more debug variables Jiri Olsa
2014-07-12 21:56 ` [PATCH 1/4] perf tools: Remove verbose from functions prototypes Jiri Olsa
2014-07-12 21:56 ` [PATCH 2/4] perf tools: Move pr_* debug macros into debug object Jiri Olsa
2014-07-12 21:56 ` [PATCH 3/4] perf tools: Factor eprintf to allow different debug variables Jiri Olsa
2014-07-12 21:56 ` [PATCH 4/4] perf tools: Add --debug optionto set debug variable Jiri Olsa
2014-07-14 7:51 ` Namhyung Kim
2014-07-14 14:51 ` Jiri Olsa [this message]
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=20140714145130.GG17761@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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
Powered by JetHome