From: Adrian Hunter <adrian.hunter@intel.com>
To: Yang Jihong <yangjihong1@huawei.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, namhyung@kernel.org, irogers@google.com,
kan.liang@linux.intel.com, james.clark@arm.com,
tmricht@linux.ibm.com, ak@linux.intel.com,
anshuman.khandual@arm.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 1/7] perf evlist: Add perf_evlist__go_system_wide() helper
Date: Fri, 4 Aug 2023 09:57:37 +0300 [thread overview]
Message-ID: <5b92986f-0e23-fa03-c322-25970cf4e2ac@intel.com> (raw)
In-Reply-To: <20230804020741.99806-2-yangjihong1@huawei.com>
On 4/08/23 05:07, Yang Jihong wrote:
> For dummy events that keep tracking, we may need to modify its cpu_maps.
> For example, change the cpu_maps to record sideband events for all CPUS.
> Add perf_evlist__go_system_wide() helper to support this scenario.
>
> Signed-off-by: Yang Jihong <yangjihong1@huawei.com>
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> tools/lib/perf/evlist.c | 9 +++++++++
> tools/lib/perf/include/internal/evlist.h | 2 ++
> 2 files changed, 11 insertions(+)
>
> diff --git a/tools/lib/perf/evlist.c b/tools/lib/perf/evlist.c
> index b8b066d0dc5e..3acbbccc1901 100644
> --- a/tools/lib/perf/evlist.c
> +++ b/tools/lib/perf/evlist.c
> @@ -738,3 +738,12 @@ int perf_evlist__nr_groups(struct perf_evlist *evlist)
> }
> return nr_groups;
> }
> +
> +void perf_evlist__go_system_wide(struct perf_evlist *evlist, struct perf_evsel *evsel)
> +{
> + if (!evsel->system_wide) {
> + evsel->system_wide = true;
> + if (evlist->needs_map_propagation)
> + __perf_evlist__propagate_maps(evlist, evsel);
> + }
> +}
> diff --git a/tools/lib/perf/include/internal/evlist.h b/tools/lib/perf/include/internal/evlist.h
> index 3339bc2f1765..d86ffe8ed483 100644
> --- a/tools/lib/perf/include/internal/evlist.h
> +++ b/tools/lib/perf/include/internal/evlist.h
> @@ -135,4 +135,6 @@ int perf_evlist__id_add_fd(struct perf_evlist *evlist,
> void perf_evlist__reset_id_hash(struct perf_evlist *evlist);
>
> void __perf_evlist__set_leader(struct list_head *list, struct perf_evsel *leader);
> +
> +void perf_evlist__go_system_wide(struct perf_evlist *evlist, struct perf_evsel *evsel);
> #endif /* __LIBPERF_INTERNAL_EVLIST_H */
next prev parent reply other threads:[~2023-08-04 6:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 2:07 [PATCH v5 0/7] perf record: Track sideband events for all CPUs when tracing selected CPUs Yang Jihong
2023-08-04 2:07 ` [PATCH v5 1/7] perf evlist: Add perf_evlist__go_system_wide() helper Yang Jihong
2023-08-04 6:57 ` Adrian Hunter [this message]
2023-08-04 2:07 ` [PATCH v5 2/7] perf evlist: Add evlist__findnew_tracking_event() helper Yang Jihong
2023-08-04 6:58 ` Adrian Hunter
2023-08-04 2:07 ` [PATCH v5 3/7] perf record: Move setting dummy tracking before record__init_thread_masks() Yang Jihong
2023-08-04 6:58 ` Adrian Hunter
2023-08-14 20:29 ` Ian Rogers
2023-08-15 1:57 ` Yang Jihong
2023-08-17 12:27 ` Yang Jihong
2023-08-04 2:07 ` [PATCH v5 4/7] perf record: Track sideband events for all CPUs when tracing selected CPUs Yang Jihong
2023-08-04 6:59 ` Adrian Hunter
2023-08-04 2:07 ` [PATCH v5 5/7] perf test: Update base-record & system-wide-dummy attr expected values for test-record-C0 Yang Jihong
2023-08-04 7:00 ` Adrian Hunter
2023-08-04 2:07 ` [PATCH v5 6/7] perf test: Add test case for record sideband events Yang Jihong
2023-08-04 7:07 ` Adrian Hunter
2023-08-04 2:07 ` [PATCH v5 7/7] perf test: Add perf_event_attr test for record selected CPUs exclude_user Yang Jihong
2023-08-04 7:08 ` Adrian Hunter
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=5b92986f-0e23-fa03-c322-25970cf4e2ac@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--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 \
--cc=tmricht@linux.ibm.com \
--cc=yangjihong1@huawei.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
all inboxes | Powered by JetHome®