From: Yang Jihong <yangjihong1@huawei.com>
To: Ian Rogers <irogers@google.com>,
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>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@arm.com>,
Suzuki Poulouse <suzuki.poulose@arm.com>,
Rob Herring <robh@kernel.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] perf pmus: Add placeholder core PMU
Date: Wed, 28 Jun 2023 11:01:47 +0800 [thread overview]
Message-ID: <344a8de1-469d-a8f9-100e-9a67e562939b@huawei.com> (raw)
In-Reply-To: <20230627182834.117565-1-irogers@google.com>
Hello,
On 2023/6/28 2:28, Ian Rogers wrote:
> If loading a core PMU fails, legacy hardware/cache events may segv due
> to there being no PMU. Create a placeholder empty PMU for this
> case. This was discussed in:
> https://lore.kernel.org/lkml/20230614151625.2077-1-yangjihong1@huawei.com/
>
> Reported-by: Yang Jihong <yangjihong1@huawei.com>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/pmu.c | 25 +++++++++++++++++++++++++
> tools/perf/util/pmu.h | 1 +
> tools/perf/util/pmus.c | 7 ++++++-
> 3 files changed, 32 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 8d5ecd4ff1a9..7f984a7f16ca 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -928,6 +928,31 @@ struct perf_pmu *perf_pmu__lookup(struct list_head *pmus, int dirfd, const char
> return NULL;
> }
>
> +/* Creates the PMU when sysfs scanning fails. */
> +struct perf_pmu *perf_pmu__create_placeholder_core_pmu(struct list_head *core_pmus)
> +{
> + struct perf_pmu *pmu = zalloc(sizeof(*pmu));
> +
> + if (!pmu)
> + return NULL;
> +
> + pmu->name = strdup("cpu");
> + if (!pmu->name) {
> + free(pmu);
> + return NULL;
> + }
> +
> + pmu->is_core = true;
> + pmu->type = PERF_TYPE_RAW;
> + pmu->cpus = cpu_map__online();
> +
> + INIT_LIST_HEAD(&pmu->format);
> + INIT_LIST_HEAD(&pmu->aliases);
> + INIT_LIST_HEAD(&pmu->caps);
> + list_add_tail(&pmu->list, core_pmus);
> + return pmu;
> +}
> +
> void perf_pmu__warn_invalid_formats(struct perf_pmu *pmu)
> {
> struct perf_pmu_format *format;
> diff --git a/tools/perf/util/pmu.h b/tools/perf/util/pmu.h
> index 8807a624e918..203b92860e3c 100644
> --- a/tools/perf/util/pmu.h
> +++ b/tools/perf/util/pmu.h
> @@ -286,6 +286,7 @@ int perf_pmu__event_source_devices_fd(void);
> int perf_pmu__pathname_fd(int dirfd, const char *pmu_name, const char *filename, int flags);
>
> struct perf_pmu *perf_pmu__lookup(struct list_head *pmus, int dirfd, const char *lookup_name);
> +struct perf_pmu *perf_pmu__create_placeholder_core_pmu(struct list_head *core_pmus);
> void perf_pmu__delete(struct perf_pmu *pmu);
>
> #endif /* __PMU_H */
> diff --git a/tools/perf/util/pmus.c b/tools/perf/util/pmus.c
> index 0866dee3fc62..3cd9de42139e 100644
> --- a/tools/perf/util/pmus.c
> +++ b/tools/perf/util/pmus.c
> @@ -153,7 +153,12 @@ static void pmu_read_sysfs(bool core_only)
>
> closedir(dir);
> if (core_only) {
> - read_sysfs_core_pmus = true;
> + if (!list_empty(&core_pmus))
> + read_sysfs_core_pmus = true;
> + else {
> + if (perf_pmu__create_placeholder_core_pmu(&core_pmus))
> + read_sysfs_core_pmus = true;
> + }
> } else {
> read_sysfs_core_pmus = true;
> read_sysfs_all_pmus = true;
>
Great. This patch solves the problem, the test results are shown in [1].
Tested-by: Yang Jihong <yangjihong1@huawei.com>
[1]:
# perf --debug verbose=2 record true
<SNIP>
------------------------------------------------------------
perf_event_attr:
size 136
{ sample_period, sample_freq } 4000
sample_type IP|TID|TIME|PERIOD
read_format ID|LOST
disabled 1
inherit 1
mmap 1
comm 1
freq 1
enable_on_exec 1
task 1
precise_ip 3
sample_id_all 1
mmap2 1
comm_exec 1
ksymbol 1
bpf_event 1
------------------------------------------------------------
sys_perf_event_open: pid 703 cpu 0 group_fd -1 flags 0x8
sys_perf_event_open failed, error -2
decreasing precise_ip by one (2)
------------------------------------------------------------
perf_event_attr:
size 136
{ sample_period, sample_freq } 4000
sample_type IP|TID|TIME|PERIOD
read_format ID|LOST
disabled 1
inherit 1
mmap 1
comm 1
freq 1
enable_on_exec 1
task 1
precise_ip 2
sample_id_all 1
mmap2 1
comm_exec 1
ksymbol 1
bpf_event 1
------------------------------------------------------------
sys_perf_event_open: pid 703 cpu 0 group_fd -1 flags 0x8
sys_perf_event_open failed, error -2
decreasing precise_ip by one (1)
------------------------------------------------------------
perf_event_attr:
size 136
{ sample_period, sample_freq } 4000
sample_type IP|TID|TIME|PERIOD
read_format ID|LOST
disabled 1
inherit 1
mmap 1
comm 1
freq 1
enable_on_exec 1
task 1
precise_ip 1
sample_id_all 1
mmap2 1
comm_exec 1
ksymbol 1
bpf_event 1
------------------------------------------------------------
sys_perf_event_open: pid 703 cpu 0 group_fd -1 flags 0x8
sys_perf_event_open failed, error -2
decreasing precise_ip by one (0)
------------------------------------------------------------
perf_event_attr:
size 136
{ sample_period, sample_freq } 4000
sample_type IP|TID|TIME|PERIOD
read_format ID|LOST
disabled 1
inherit 1
mmap 1
comm 1
freq 1
enable_on_exec 1
task 1
sample_id_all 1
mmap2 1
comm_exec 1
ksymbol 1
bpf_event 1
------------------------------------------------------------
sys_perf_event_open: pid 703 cpu 0 group_fd -1 flags 0x8
sys_perf_event_open failed, error -2
Warning:
The cycles event is not supported, trying to fall back to cpu-clock-ticks
------------------------------------------------------------
perf_event_attr:
type 1
size 136
{ sample_period, sample_freq } 4000
sample_type IP|TID|TIME|PERIOD
read_format ID|LOST
disabled 1
inherit 1
mmap 1
comm 1
freq 1
enable_on_exec 1
task 1
precise_ip 3
sample_id_all 1
mmap2 1
comm_exec 1
ksymbol 1
bpf_event 1
------------------------------------------------------------
sys_perf_event_open: pid 703 cpu 0 group_fd -1 flags 0x8 = 5
sys_perf_event_open: pid 703 cpu 1 group_fd -1 flags 0x8 = 6
sys_perf_event_open: pid 703 cpu 2 group_fd -1 flags 0x8 = 7
sys_perf_event_open: pid 703 cpu 3 group_fd -1 flags 0x8 = 9
sys_perf_event_open: pid 703 cpu 4 group_fd -1 flags 0x8 = 10
sys_perf_event_open: pid 703 cpu 5 group_fd -1 flags 0x8 = 11
sys_perf_event_open: pid 703 cpu 6 group_fd -1 flags 0x8 = 12
sys_perf_event_open: pid 703 cpu 7 group_fd -1 flags 0x8 = 13
<SNIP>
[ perf record: Captured and wrote 0.006 MB perf.data (116 samples) ]
Thanks,
Yang
next prev parent reply other threads:[~2023-06-28 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 18:28 Ian Rogers
2023-06-28 3:01 ` Yang Jihong [this message]
2023-06-28 20:05 ` Namhyung Kim
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=344a8de1-469d-a8f9-100e-9a67e562939b@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.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=ravi.bangoria@amd.com \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.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®