From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andi Kleen <ak@linux.intel.com>, David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 5/9] perf tools: Set maximum precise value for event 'p' modifier
Date: Fri, 10 May 2013 10:53:41 +0900 [thread overview]
Message-ID: <8738tv7g7u.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1368106344-23383-6-git-send-email-jolsa@redhat.com> (Jiri Olsa's message of "Thu, 9 May 2013 15:32:20 +0200")
On Thu, 9 May 2013 15:32:20 +0200, Jiri Olsa wrote:
> If single 'p' modifier is specified for event, set the
> system precise value for perf_events_attr::precise_ip.
>
> If more than a single 'p' is specified keep the intended
> value.
So there's no way to set precise=1 on a system suppports precise=2 using
this syntax, right? (I don't know whether it makes any sense though.)
>
> If precise is not supported by system, warning is disaplyed.
s/disaplyed/displayed/
>
> Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Stephane Eranian <eranian@google.com>
> ---
> tools/perf/util/parse-events.c | 40 ++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 38 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
> index 2e3ef10..6be4599 100644
> --- a/tools/perf/util/parse-events.c
> +++ b/tools/perf/util/parse-events.c
> @@ -533,6 +533,26 @@ int parse_events_add_breakpoint(struct list_head **list, int *idx,
> return add_event(list, idx, &attr, NULL);
> }
>
> +static int precise_default(void)
> +{
> + int precise = perf_precise__get();
> + static int warned;
> +
> + /*
> + * Precise info not supported by by this kernel,
s/by by/by/ :)
> + * set 1 as the precise value.
> + */
> + if (precise == -1)
> + precise = 1;
> +
> + /* PEBS is not supported here, display warning. */
> + if (precise == 0 && !warned++)
> + pr_warning("warning: no precise support, "
> + "using non-precise event(s)\n");
Please put the message on a single line.
Thanks,
Namhyung
next prev parent reply other threads:[~2013-05-10 1:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 13:32 [PATCH 0/9] perf: Adding better precise_ip field handling Jiri Olsa
2013-05-09 13:32 ` [PATCH 1/9] perf x86: Add precise sysfs cpu pmu attribute Jiri Olsa
2013-05-09 13:32 ` [PATCH 2/9] perf tools: Add precise object to interface sysfs precise Jiri Olsa
2013-05-10 1:34 ` Namhyung Kim
2013-05-10 9:06 ` Jiri Olsa
2013-05-09 13:32 ` [PATCH 3/9] perf tests: Add precise event automated test Jiri Olsa
2013-05-09 13:32 ` [PATCH 4/9] perf tools: Add a precise event qualifier Jiri Olsa
2013-05-10 1:43 ` Namhyung Kim
2013-05-10 9:10 ` Jiri Olsa
2013-05-09 13:32 ` [PATCH 5/9] perf tools: Set maximum precise value for event 'p' modifier Jiri Olsa
2013-05-09 19:43 ` David Ahern
2013-05-10 9:12 ` Jiri Olsa
2013-05-10 1:53 ` Namhyung Kim [this message]
2013-05-10 9:16 ` Jiri Olsa
2013-05-09 13:32 ` [PATCH 6/9] perf tools: Set maximum precise value for 'precise' term Jiri Olsa
2013-05-09 13:32 ` [PATCH 7/9] perf tests: Add automated precise term test Jiri Olsa
2013-05-09 13:32 ` [PATCH 8/9] perf: Document the ABI for 'precise' sysfs attribute Jiri Olsa
2013-05-10 1:57 ` Namhyung Kim
2013-05-09 13:32 ` [PATCH 9/9] perf: Document the ABI for 'rdpmc' " Jiri Olsa
2013-05-09 15:07 ` [PATCH 0/9] perf: Adding better precise_ip field handling Peter Zijlstra
2013-05-09 15:20 ` Jiri Olsa
2013-05-10 9:27 ` Peter Zijlstra
2013-05-10 9:40 ` Jiri Olsa
2013-05-10 9:53 ` Peter Zijlstra
2013-05-10 10:18 ` Ingo Molnar
2013-05-10 10:22 ` Peter Zijlstra
2013-05-10 10:31 ` Ingo Molnar
2013-05-10 10:34 ` Peter Zijlstra
2013-05-10 10:55 ` Ingo Molnar
2013-05-10 11:27 ` Peter Zijlstra
2013-05-11 7:50 ` Ingo Molnar
2013-05-13 9:36 ` Peter Zijlstra
2013-05-13 19:43 ` Ingo Molnar
2013-05-14 7:22 ` Peter Zijlstra
2013-05-14 8:37 ` Ingo Molnar
2013-05-14 8:36 ` Gleb Natapov
2013-05-15 13:27 ` Stephane Eranian
2013-05-28 9:54 ` Ingo Molnar
2013-05-10 9:29 ` Peter Zijlstra
2013-05-10 9:43 ` 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=8738tv7g7u.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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