From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Dapeng Mi <dapeng1.mi@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Dapeng Mi <dapeng1.mi@intel.com>
Subject: Re: [PATCH] perf topdown: Correct leader selection with sample_read enabled
Date: Thu, 27 Jun 2024 11:11:05 -0400 [thread overview]
Message-ID: <df56c6e1-5d99-4cbe-abd4-772e7ff948af@linux.intel.com> (raw)
In-Reply-To: <20240614213908.352840-1-dapeng1.mi@linux.intel.com>
Hi Dapeng,
On 2024-06-14 5:39 p.m., Dapeng Mi wrote:
> Addresses an issue where, in the absence of a topdown metrics event
> within a sampling group, the slots event was incorrectly bypassed as
> the sampling leader when sample_read was enabled.
>
> perf record -e '{slots,branches}:S' -c 10000 -vv sleep 1
>
> In this case, the slots event should be sampled as leader but the
> branches event is sampled in fact like the verbose output shows.
>
> perf_event_attr:
> type 4 (cpu)
> size 168
> config 0x400 (slots)
> sample_type IP|TID|TIME|READ|CPU|IDENTIFIER
> read_format ID|GROUP|LOST
> disabled 1
> sample_id_all 1
> exclude_guest 1
> ------------------------------------------------------------
> sys_perf_event_open: pid -1 cpu 0 group_fd -1 flags 0x8 = 5
> ------------------------------------------------------------
> perf_event_attr:
> type 0 (PERF_TYPE_HARDWARE)
> size 168
> config 0x4 (PERF_COUNT_HW_BRANCH_INSTRUCTIONS)
> { sample_period, sample_freq } 10000
> sample_type IP|TID|TIME|READ|CPU|IDENTIFIER
> read_format ID|GROUP|LOST
> sample_id_all 1
> exclude_guest 1
>
> The sample period of slots event instead of branches event is reset to
> 0.
>
> This fix ensures the slots event remains the leader under these
> conditions.
This should be just one of the issues with the slots/topdown related
sampling read.
If adding one more topdown event, the sampling read may still be broken.
perf record -e "{slots,instructions,topdown-retiring}:S" -C0 sleep 1
WARNING: events were regrouped to match PMUs
Error:
The sys_perf_event_open() syscall returned with 22 (Invalid argument)
for event (topdown-retiring).
That may require Yanfei's patch.
https://lore.kernel.org/lkml/20240411144852.2507143-1-yanfei.xu@intel.com/
Please give it try and summarize all the required patches for the
topdown sampling read feature.
Besides, we need a test for the sampling read as well.
Ian has provided a very good base. Please add a topdown sampling read
case on top of it as well.
https://lore.kernel.org/lkml/CAP-5=fUkg-cAXTb+3wbFOQCfdXgpQeZw40XHjfrNFbnBD=NMXg@mail.gmail.com/
Thanks,
Kan
>
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
> ---
> tools/perf/arch/x86/util/topdown.c | 42 ++++++++++++++++++++++++++++--
> 1 file changed, 40 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/arch/x86/util/topdown.c b/tools/perf/arch/x86/util/topdown.c
> index 3f9a267d4501..aea6896bbb57 100644
> --- a/tools/perf/arch/x86/util/topdown.c
> +++ b/tools/perf/arch/x86/util/topdown.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0
> #include "api/fs/fs.h"
> #include "util/evsel.h"
> +#include "util/evlist.h"
> #include "util/pmu.h"
> #include "util/pmus.h"
> #include "util/topdown.h"
> @@ -31,6 +32,32 @@ bool topdown_sys_has_perf_metrics(void)
> return has_perf_metrics;
> }
>
> +static int perf_pmus__topdown_event(void *vstate, struct pmu_event_info *info)
> +{
> + if (!strcmp(info->name, (char *)vstate))
> + return 1;
> +
> + return 0;
> +}
> +
> +static bool is_topdown_metric_event(struct evsel *event)
> +{
> + struct perf_pmu *pmu;
> +
> + if (!topdown_sys_has_perf_metrics())
> + return false;
> +
> + if (event->core.attr.type != PERF_TYPE_RAW)
> + return false;
> +
> + pmu = perf_pmus__find_by_type(PERF_TYPE_RAW);
> + if (pmu && perf_pmu__for_each_event(pmu, false, event->name,
> + perf_pmus__topdown_event))
> + return true;
> +
> + return false;
> +}
> +
> #define TOPDOWN_SLOTS 0x0400
>
> /*
> @@ -41,11 +68,22 @@ bool topdown_sys_has_perf_metrics(void)
> */
> bool arch_topdown_sample_read(struct evsel *leader)
> {
> + struct evsel *event;
> +
> if (!evsel__sys_has_perf_metrics(leader))
> return false;
>
> - if (leader->core.attr.config == TOPDOWN_SLOTS)
> - return true;
> + if (leader->core.attr.config != TOPDOWN_SLOTS)
> + return false;
> +
> + /*
> + * If slots event as leader event but no topdown metric events in group,
> + * slots event should still sample as leader.
> + */
> + evlist__for_each_entry(leader->evlist, event) {
> + if (event != leader && is_topdown_metric_event(event))
> + return true;
> + }
>
> return false;
> }
>
> base-commit: 92e5605a199efbaee59fb19e15d6cc2103a04ec2
next prev parent reply other threads:[~2024-06-27 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 21:39 [PATCH] perf topdown: Correct leader selection with sample_read enabled Dapeng Mi
2024-06-27 15:11 ` Liang, Kan [this message]
2024-06-28 6:17 ` Mi, Dapeng
2024-06-28 18:28 ` Ian Rogers
2024-06-28 20:27 ` Liang, Kan
2024-07-01 9:51 ` Mi, Dapeng
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=df56c6e1-5d99-4cbe-abd4-772e7ff948af@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--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).