mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	<kan.liang@linux.intel.com>, <peterz@infradead.org>,
	<mingo@redhat.com>, <acme@kernel.org>, <namhyung@kernel.org>,
	<irogers@google.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf/x86/intel: Clean up PEBS-via-PT on hybrid
Date: Mon, 27 Jan 2025 13:42:34 +0200	[thread overview]
Message-ID: <1954a8b1-83f0-4959-98d3-743662fc7de2@intel.com> (raw)
In-Reply-To: <87y0ywzj7o.fsf@ubik.fi.intel.com>

On 27/01/25 11:42, Alexander Shishkin wrote:
> [sending again, because smtp is hard, for some reason]
> kan.liang@linux.intel.com writes:
> 
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> The PEBS-via-PT feature is exposed for the e-core of some hybrid
>> platforms, e.g., ADL and MTL. But it never works.
>>
>> $ dmesg | grep PEBS
>> [    1.793888] core: cpu_atom PMU driver: PEBS-via-PT
>>
>> $ perf record -c 1000 -e '{intel_pt/branch=0/,
>> cpu_atom/cpu-cycles,aux-output/pp}' -C8
>> Error:
>> The sys_perf_event_open() syscall returned with 22 (Invalid argument)
>> for event (cpu_atom/cpu-cycles,aux-output/pp).
>> "dmesg | grep -i perf" may provide additional information.
>>
>> The "PEBS-via-PT" is printed if the corresponding bit of per-PMU
>> capabilities is set. Since the feature is supported by the e-core HW,
>> perf sets the bit for e-core. However, for Intel PT, if a feature is not
>> supported on all CPUs, it is not supported at all. The PEBS-via-PT event
>> cannot be created successfully.
>>
>> The PEBS-via-PT is no longer enumerated on the latest hybrid platform. It
>> will be deprecated on future platforms with Arch PEBS. Let's remove it
>> from the existing hybrid platforms.
> 
> There are still lots of them in use in the wild, I'd still like to fix
> this properly instead of chopping it off. Unless there's a reason not to?

The kernel has never supported PEBS-via-PT on hybrids before.
AFAIK no one is asking for it on hybrids.

Note, it will continue to work on non-hybrid atom/e-core systems
like ADL-N etc


  reply	other threads:[~2025-01-27 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 18:34 kan.liang
2025-01-27  8:19 ` Adrian Hunter
2025-01-27 14:34   ` Liang, Kan
2025-01-27  9:42 ` Alexander Shishkin
2025-01-27 11:42   ` Adrian Hunter [this message]
2025-01-27 14:41     ` Liang, Kan

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=1954a8b1-83f0-4959-98d3-743662fc7de2@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®