From: Ingo Molnar <mingo@elte.hu>
To: "Xu, Anhua" <anhua.xu@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: perf tools: interface for improved PEBS ABI can accept wrong parameter
Date: Tue, 18 Oct 2011 20:19:43 +0200 [thread overview]
Message-ID: <20111018181943.GC21666@elte.hu> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B212DC93638A@shsmsx501.ccr.corp.intel.com>
Added more Cc:s of maintainers.
thanks,
Ingo
* Xu, Anhua <anhua.xu@intel.com> wrote:
> For the commit: ab60834 perf, x86: Improve the PEBS ABI
> The precise_ip is restricted to 2 bits. The values larger than 3 are truncated less or equal to 3.
> This can effectively restricted value passing to syscall. But the user space interface can accept other wrong values which are larger than 3 and lowest 2 bits are 0 can meet the requirement.
>
> # Here is an example, Monitor "All branches" events on Sandybridge platform( Please refer to SDM 3B Table 30-21 to check Sandybridge specific events )
>
> perf top -e r04c4:p # precise_ip = 1 , Correct
> perf top -e r04c4:pp # precise_ip =2, Correct
> perf top -e r04c4:ppp # not supported, Correct
> perf top -e r04c4:pppppp # should not be supported, but after truncation , the number of 'p' treated as 2 which is accepted
>
>
> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> index c816075..07d3cf9 100644
> --- a/include/linux/perf_event.h
> +++ b/include/linux/perf_event.h
> @@ -216,6 +216,7 @@ struct perf_event_attr {
> *
> * See also PERF_RECORD_MISC_EXACT_IP
> */
> +#define SAMPLE_IP_MAX 3
> precise_ip : 2, /* skid constraint */
> mmap_data : 1, /* non-exec mmap data */
> sample_id_all : 1, /* sample_type all events */
> diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
> index 928918b..a2068cc 100644
> --- a/tools/perf/util/parse-events.c
> +++ b/tools/perf/util/parse-events.c
> @@ -775,7 +775,10 @@ parse_event_modifier(const char **strp, struct perf_event_attr *attr)
> attr->exclude_user = eu;
> attr->exclude_kernel = ek;
> attr->exclude_hv = eh;
> - attr->precise_ip = precise;
> + if ( precise < SAMPLE_IP_MAX )
> + attr->precise_ip = precise;
> + else
> + return -1;
>
> return 0;
> }
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Thanks,
Ingo
next prev parent reply other threads:[~2011-10-18 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 14:31 Xu, Anhua
2011-10-18 18:19 ` Ingo Molnar [this message]
2011-10-18 18:28 ` Peter Zijlstra
2011-10-19 2:23 ` Xu, Anhua
2011-10-19 3:06 ` Chen Gong
2011-10-19 14:15 ` Arnaldo Carvalho de Melo
2011-10-23 17:07 ` Xu, Anhua
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 14:20 Xu, Anhua
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=20111018181943.GC21666@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=anhua.xu@intel.com \
--cc=linux-kernel@vger.kernel.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