From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com,
like.xu@linux.intel.com
Subject: Re: [PATCH] perf parse-events: Set exclude_guest for user-space counting
Date: Wed, 12 Aug 2020 09:55:26 -0300 [thread overview]
Message-ID: <20200812125526.GM13995@kernel.org> (raw)
In-Reply-To: <20200812121504.GE13995@kernel.org>
Em Wed, Aug 12, 2020 at 09:15:04AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Aug 12, 2020 at 02:59:53PM +0800, Jin Yao escreveu:
> > Currently if we run 'perf record -e cycles:u', exclude_guest is 0.
> >
> > But it doesn't make sense that we request for user-space counting
> > but we also get the guest report.
> >
> > To keep perf semantics consistent and clear, this patch sets
> > exclude_guest for user-space counting.
>
> Applied, and also added this, that you should consider doing in the
> future (modulo the "Committer testing:" header :) ):
>
> Committer testing:
>
> Before:
>
> # perf record -e cycles:u
> ^C[ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 1.231 MB perf.data (91 samples) ]
> #
> # perf evlist -v
> cycles:u: size: 120, { sample_period, sample_freq }: 4000, sample_type: IP|TID|TIME|ID|CPU|PERIOD, read_format: ID, disabled: 1, inherit: 1, exclude_kernel: 1, exclude_hv: 1, freq: 1, sample_id_all: 1
> <SNIP>
> #
>
> After:
>
> # perf record -e cycles:u
> ^C[ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 1.263 MB perf.data (403 samples) ]
> #
> # perf evlist -v
> cycles:u: size: 120, { sample_period, sample_freq }: 4000, sample_type: IP|TID|TIME|ID|CPU|PERIOD, read_format: ID, disabled: 1, inherit: 1, exclude_kernel: 1, exclude_hv: 1, freq: 1, sample_id_all: 1, exclude_guest: 1
> #
Also, please run 'perf test', as this will require changes to some
expected perf_event_attr setups:
[root@quaco ~]# perf test "event definition"
6: Parse event definition strings : FAILED!
[root@quaco ~]#
- Arnaldo
next prev parent reply other threads:[~2020-08-12 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 6:59 [PATCH] perf parse-events: Set exclude_guest for user-space counting Jin Yao
2020-08-12 12:15 ` Arnaldo Carvalho de Melo
2020-08-12 12:55 ` Arnaldo Carvalho de Melo [this message]
2020-08-13 5:09 ` Jin, Yao
2020-08-12 13:02 ` Like Xu
2020-08-13 3:11 ` Jin, Yao
2020-08-13 6:57 ` Like Xu
2020-08-13 7:08 ` Jin, Yao
2020-08-13 7:21 ` Like Xu
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=20200812125526.GM13995@kernel.org \
--to=acme@kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=like.xu@linux.intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.intel.com \
/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