From: Slade Watkins <srw@sladewatkins.net>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: linux-perf-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>
Subject: Re: Invalid event (cycles:pp) in per-thread mode, enable system wide with '-a'.
Date: Thu, 29 Sep 2022 18:10:35 -0400 [thread overview]
Message-ID: <76CB17D0-5A66-4D49-A389-8F40EC830DC0@sladewatkins.net> (raw)
In-Reply-To: <CAKwvOdnrHErOK+w878izVauHUKaX3eD-HXgigq2Ogm3iSj-fHA@mail.gmail.com>
Hey Nick,
> On Sep 29, 2022, at 5:54 PM, Nick Desaulniers <ndesaulniers@google.com> wrote:
>
> I remember hearing rumblings about issues with zen 2, LBR, vs zen 3.
> Is this a known issue, or am I holding it wrong?
Hm… I also remember this. I have a Zen 2 based system that I can do testing on, so I will do so when I’m able.
If I discover something of note, I’ll get back to you.
Cheers,
-srw
next prev parent reply other threads:[~2022-09-29 22:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 21:54 Invalid event (cycles:pp) in per-thread mode, enable system wide with '-a' Nick Desaulniers
2022-09-29 22:10 ` Slade Watkins [this message]
2022-09-30 3:23 ` Ian Rogers
2022-09-30 4:26 ` Namhyung Kim
2022-09-30 4:31 ` Ravi Bangoria
2022-10-05 21:55 ` Nick Desaulniers
2022-10-05 22:50 ` Stephane Eranian
2022-10-07 3:56 ` Ravi Bangoria
2022-10-11 21:32 ` Nick Desaulniers
2022-10-12 4:06 ` Ravi Bangoria
2022-10-12 5:04 ` Ravi Bangoria
2023-06-23 16:23 ` Nick Desaulniers
2023-06-23 23:18 ` Namhyung Kim
2023-06-26 5:44 ` Ravi Bangoria
2023-07-10 21:22 ` Nick Desaulniers
2023-07-11 5:14 ` Ravi Bangoria
2022-10-11 21:38 ` Nick Desaulniers
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=76CB17D0-5A66-4D49-A389-8F40EC830DC0@sladewatkins.net \
--to=srw@sladewatkins.net \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).