mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@arm.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Perry Taylor <perry.taylor@intel.com>,
	Samantha Alt <samantha.alt@intel.com>,
	Caleb Biggers <caleb.biggers@intel.com>,
	Weilin Wang <weilin.wang@intel.com>,
	Edward Baker <edward.baker@intel.com>
Subject: Re: [PATCH v1] perf pmu: Treat the msr pmu as software
Date: Thu, 25 Jan 2024 09:48:22 -0500	[thread overview]
Message-ID: <31c90c4d-f6db-4f98-9b38-83260b0f8aa2@linux.intel.com> (raw)
In-Reply-To: <20240124234200.1510417-1-irogers@google.com>



On 2024-01-24 6:42 p.m., Ian Rogers wrote:
> The msr PMU is a software one, meaning msr events may be grouped
> with events in a hardware context. As the msr PMU isn't marked as a
> software PMU by perf_pmu__is_software, groups with the msr PMU in
> are broken and the msr events placed in a different group. This
> may lead to multiplexing errors where a hardware event isn't
> counted while the msr event, such as tsc, is. Fix all of this by
> marking the msr PMU as software, which agrees with the driver.

Yes, the MSR PMU is in SW context, perf_sw_context.

Reviewed-by: Kan Liang <kan.liang@linux.intel.com>

Thanks,
Kan

> 
> Before:
> ```
> $ perf stat -e '{slots,tsc}' -a true
> WARNING: events were regrouped to match PMUs
> 
>  Performance counter stats for 'system wide':
> 
>          1,750,335      slots
>          4,243,557      tsc
> 
>        0.001456717 seconds time elapsed
> ```
> 
> After:
> ```
> $ perf stat -e '{slots,tsc}' -a true
>  Performance counter stats for 'system wide':
> 
>         12,526,380      slots
>          3,415,163      tsc
> 
>        0.001488360 seconds time elapsed
> ```
> 
> Fixes: 251aa040244a ("perf parse-events: Wildcard most "numeric" events")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> The fixes tag is close enough rather than being fully accurate. The
> regression was introduced earlier by the automatic event regrouping.
> ---
>  tools/perf/util/pmu.c | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 3c9609944a2f..88b9aa7d3a27 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -1760,6 +1760,12 @@ bool pmu__name_match(const struct perf_pmu *pmu, const char *pmu_name)
>  
>  bool perf_pmu__is_software(const struct perf_pmu *pmu)
>  {
> +	const char *known_sw_pmus[] = {
> +		"kprobe",
> +		"msr",
> +		"uprobe",
> +	};
> +
>  	if (pmu->is_core || pmu->is_uncore || pmu->auxtrace)
>  		return false;
>  	switch (pmu->type) {
> @@ -1771,7 +1777,11 @@ bool perf_pmu__is_software(const struct perf_pmu *pmu)
>  	case PERF_TYPE_BREAKPOINT:	return true;
>  	default: break;
>  	}
> -	return !strcmp(pmu->name, "kprobe") || !strcmp(pmu->name, "uprobe");
> +	for (size_t i = 0; i < ARRAY_SIZE(known_sw_pmus); i++) {
> +		if (!strcmp(pmu->name, known_sw_pmus[i]))
> +			return true;
> +	}
> +	return false;
>  }
>  
>  FILE *perf_pmu__open_file(const struct perf_pmu *pmu, const char *name)

  reply	other threads:[~2024-01-25 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 23:42 Ian Rogers
2024-01-25 14:48 ` Liang, Kan [this message]
2024-01-27 18:16 ` 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=31c90c4d-f6db-4f98-9b38-83260b0f8aa2@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=caleb.biggers@intel.com \
    --cc=edward.baker@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --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=perry.taylor@intel.com \
    --cc=peterz@infradead.org \
    --cc=samantha.alt@intel.com \
    --cc=weilin.wang@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

all inboxes | Powered by JetHome®