From: Jiri Olsa <jolsa@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf record: add dummy event during system wide synthesis
Date: Mon, 20 Apr 2020 10:43:39 +0200 [thread overview]
Message-ID: <20200420083720.GB718574@krava> (raw)
In-Reply-To: <20200416004713.192740-1-irogers@google.com>
On Wed, Apr 15, 2020 at 05:47:13PM -0700, Ian Rogers wrote:
> During the processing of /proc during event synthesis new processes may
> start. Add a dummy event if /proc is to be processed, to capture mmaps
> for starting processes. This reuses the existing logic for
> initial-delay.
>
> Suggested-by: Stephane Eranian <eranian@google.com>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/builtin-record.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 1ab349abe904..bab4fc8568d1 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -805,16 +805,18 @@ static int record__open(struct record *rec)
> int rc = 0;
>
> /*
> - * For initial_delay we need to add a dummy event so that we can track
> - * PERF_RECORD_MMAP while we wait for the initial delay to enable the
> - * real events, the ones asked by the user.
> + * For initial_delay or system wide, we need to add a dummy event so
> + * that we can track PERF_RECORD_MMAP to cover the delay (of waiting or
> + * synthesis) prior to the real user events being enabled.
> */
> - if (opts->initial_delay) {
> + if (opts->initial_delay || target__has_cpu(&opts->target)) {
hum, how this works for system wide? IIRC the delay works
for monitoring tasks by setting dummy with enable_on_exec,
and enabling the rest by ioctl after the delay.. so without
the monitored task there's no enable_on_exec effect
jirka
> if (perf_evlist__add_dummy(evlist))
> return -ENOMEM;
>
> + /* Disable tracking of mmaps on lead event. */
> pos = evlist__first(evlist);
> pos->tracking = 0;
> + /* Activate dummy event immediately. */
> pos = evlist__last(evlist);
> pos->tracking = 1;
> pos->core.attr.enable_on_exec = 1;
> --
> 2.26.0.110.g2183baf09c-goog
>
next prev parent reply other threads:[~2020-04-20 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 0:47 [PATCH] perf record: add dummy event during system wide synthesis Ian Rogers
2020-04-20 8:43 ` Jiri Olsa [this message]
2020-04-21 6:17 ` Ian Rogers
2020-04-24 8:51 ` [perf record] dbfc8ef0b9: perf-sanity-tests.Setup_struct_perf_event_attr.fail kernel test robot
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=20200420083720.GB718574@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).