linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Pasi Kallinen <paxed@alt.org>,
	1104796@bugs.debian.org, Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, regressions@lists.linux.dev,
	Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Re: perf r5101c4 counter regression
Date: Thu, 8 May 2025 13:56:50 -0700	[thread overview]
Message-ID: <aB0akj1BdBeY6YiI@google.com> (raw)
In-Reply-To: <aBpcvG2yBtrrTie-@eldamar.lan>

Hello,

On Tue, May 06, 2025 at 09:02:20PM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> Pasi Kallinen reported in Debian a regression with perf r5101c4
> counter, initially it was found in
> https://github.com/rr-debugger/rr/issues/3949 but said to be a kernel
> problem.

What's the '51' part?  I don't think it's defined.

  $ grep . -r /sys/bus/event_source/devices/cpu/format/
  /sys/bus/event_source/devices/cpu/format/event:config:0-7
  /sys/bus/event_source/devices/cpu/format/pc:config:19
  /sys/bus/event_source/devices/cpu/format/edge:config:18
  /sys/bus/event_source/devices/cpu/format/offcore_rsp:config1:0-63
  /sys/bus/event_source/devices/cpu/format/ldlat:config1:0-15
  /sys/bus/event_source/devices/cpu/format/inv:config:23
  /sys/bus/event_source/devices/cpu/format/umask:config:8-15
  /sys/bus/event_source/devices/cpu/format/frontend:config1:0-23
  /sys/bus/event_source/devices/cpu/format/cmask:config:24-31


Nothing for bit 16, 20 and 22 on the 'config' field.

Is it possible to fix rr to use a correct event encoding instead?

Thanks,
Namhyung

> 
> On Tue, May 06, 2025 at 07:18:39PM +0300, Pasi Kallinen wrote:
> > Package: src:linux
> > Version: 6.12.25-1
> > Severity: normal
> > X-Debbugs-Cc: debian-amd64@lists.debian.org, paxed@alt.org
> > User: debian-amd64@lists.debian.org
> > Usertags: amd64
> > 
> > Dear Maintainer,
> > 
> > perf stat -e r5101c4 true
> > 
> > reports "not supported".
> > 
> > The counters worked in kernel 6.11.10.
> > 
> > I first noticed this not working when updating to 6.12.22.
> > Booting back to 6.11.10, the counters work correctly.
> 
> Does this ring a bell?
> 
> Would you be able to bisect the changes to identify where the
> behaviour changed?
> 
> Regards,
> Salvatore

      reply	other threads:[~2025-05-08 20:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <174654831962.2704.6099474499200154093.reportbug@deveel>
2025-05-06 19:02 ` perf r5101c4 counter regression Salvatore Bonaccorso
2025-05-08 20:56   ` Namhyung Kim [this message]

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=aB0akj1BdBeY6YiI@google.com \
    --to=namhyung@kernel.org \
    --cc=1104796@bugs.debian.org \
    --cc=acme@kernel.org \
    --cc=carnil@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paxed@alt.org \
    --cc=peterz@infradead.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=submit@bugs.debian.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).