From: David Ahern <dsahern@gmail.com>
To: Andrew Vagin <avagin@openvz.org>
Cc: linux-kernel@vger.kernel.org, Arun Sharma <asharma@fb.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
devel@openvz.org
Subject: Re: [PATCH 4/7] perf: add ability to change event according to sample
Date: Mon, 07 Nov 2011 14:14:39 -0700 [thread overview]
Message-ID: <4EB84A3F.5060501@gmail.com> (raw)
In-Reply-To: <1320670457-2633428-5-git-send-email-avagin@openvz.org>
On 11/07/2011 05:54 AM, Andrew Vagin wrote:
> It's opposition of perf_session__parse_sample.
>
> Signed-off-by: Andrew Vagin <avagin@openvz.org>
> ---
> tools/perf/util/event.h | 2 +
> tools/perf/util/evsel.c | 74 +++++++++++++++++++++++++++++++++++++++++++++
> tools/perf/util/session.h | 9 +++++
> 3 files changed, 85 insertions(+), 0 deletions(-)
>
> diff --git a/tools/perf/util/event.h b/tools/perf/util/event.h
> index 357a85b..0493101 100644
> --- a/tools/perf/util/event.h
> +++ b/tools/perf/util/event.h
> @@ -187,5 +187,7 @@ const char *perf_event__name(unsigned int id);
> int perf_event__parse_sample(const union perf_event *event, u64 type,
> int sample_size, bool sample_id_all,
> struct perf_sample *sample, bool swapped);
> +int perf_event__change_sample(union perf_event *event, u64 type,
> + const struct perf_sample *data, bool swapped);
>
> #endif /* __PERF_RECORD_H */
> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> index b46f6e4..9274e08 100644
> --- a/tools/perf/util/evsel.c
> +++ b/tools/perf/util/evsel.c
> @@ -475,3 +475,77 @@ int perf_event__parse_sample(const union perf_event *event, u64 type,
>
> return 0;
> }
> +
> +int perf_event__change_sample(union perf_event *event, u64 type,
> + const struct perf_sample *data, bool swapped)
> +{
> + u64 *array;
> +
> + /*
> + * used for cross-endian analysis. See git commit 65014ab3
> + * for why this goofiness is needed.
> + */
> + union {
> + u64 val64;
> + u32 val32[2];
> + } u;
> +
> + array = event->sample.array;
> +
> + if (type & PERF_SAMPLE_IP) {
> + event->ip.ip = data->ip;
> + array++;
> + }
> +
> + if (type & PERF_SAMPLE_TID) {
> + u.val32[0] = data->pid;
> + u.val32[1] = data->tid;
> + if (swapped) {
> + /* undo swap of u64, then swap on individual u32s */
> + u.val64 = bswap_64(u.val64);
> + u.val32[0] = bswap_32(u.val32[0]);
> + u.val32[1] = bswap_32(u.val32[1]);
If this is meant to be the reverse direction of parse_sample then I
think you need the bswap_64 after the bswap_32.
> + }
> +
> + *array = u.val64;
> + array++;
> + }
> +
> + if (type & PERF_SAMPLE_TIME) {
> + *array = data->time;
> + array++;
> + }
> +
> + if (type & PERF_SAMPLE_ADDR) {
> + *array = data->addr;
> + array++;
> + }
> +
> + if (type & PERF_SAMPLE_ID) {
> + *array = data->id;
> + array++;
> + }
> +
> + if (type & PERF_SAMPLE_STREAM_ID) {
> + *array = data->stream_id;
> + array++;
> + }
> +
> + if (type & PERF_SAMPLE_CPU) {
> + u.val32[0] = data->cpu;
> + if (swapped) {
> + /* undo swap of u64, then swap on individual u32s */
> + u.val64 = bswap_64(u.val64);
> + u.val32[0] = bswap_32(u.val32[0]);
> + }
Ditto here too.
This really should be tested for cross-endian analysis to verify it
works properly.
David
> + *array = u.val64;
> + array++;
> + }
> +
> + if (type & PERF_SAMPLE_PERIOD) {
> + *array = data->period;
> + array++;
> + }
> +
> + return 0;
> +}
> diff --git a/tools/perf/util/session.h b/tools/perf/util/session.h
> index 514b06d..5a36d10 100644
> --- a/tools/perf/util/session.h
> +++ b/tools/perf/util/session.h
> @@ -166,6 +166,15 @@ static inline int perf_session__parse_sample(struct perf_session *session,
> session->header.needs_swap);
> }
>
> +static inline int perf_session__change_sample(struct perf_session *session,
> + union perf_event *event,
> + const struct perf_sample *sample)
> +{
> + return perf_event__change_sample(event, session->sample_type,
> + sample,
> + session->header.needs_swap);
> +}
> +
> struct perf_evsel *perf_session__find_first_evtype(struct perf_session *session,
> unsigned int type);
>
next prev parent reply other threads:[~2011-11-07 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 12:54 [PATCH 0/7] Profiling sleep times (v2) Andrew Vagin
2011-11-07 12:54 ` [PATCH 1/7] perf: use event_name() to get an event name Andrew Vagin
2011-11-07 12:54 ` [PATCH 2/7] event: don't divide events if it has field period Andrew Vagin
2011-11-09 11:55 ` Peter Zijlstra
2011-11-11 9:54 ` Andrew Vagin
2011-11-17 8:22 ` Andrew Wagin
2011-11-17 8:45 ` Peter Zijlstra
2011-11-18 23:36 ` [tip:perf/core] events: Don't " tip-bot for Andrew Vagin
2011-11-07 12:54 ` [PATCH 3/7] perf: add ability to record event period Andrew Vagin
2011-11-07 12:54 ` [PATCH 4/7] perf: add ability to change event according to sample Andrew Vagin
2011-11-07 21:14 ` David Ahern [this message]
2011-11-07 12:54 ` [PATCH 5/7] perf: teach "perf inject" to work with files Andrew Vagin
2011-11-07 12:54 ` [PATCH 6/7] perf: teach perf inject to merge sched_stat_* and sched_switch events Andrew Vagin
2011-11-07 12:54 ` [PATCH 7/7] perf: add scripts for profiling sleep times Andrew Vagin
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=4EB84A3F.5060501@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=asharma@fb.com \
--cc=avagin@openvz.org \
--cc=devel@openvz.org \
--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;
as well as URLs for NNTP newsgroup(s).