linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Nick Desaulniers <ndesaulniers@google.com>,
	Namhyung Kim <namhyung@gmail.com>
Cc: Stephane Eranian <eranian@google.com>,
	Slade Watkins <srw@sladewatkins.net>,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ian Rogers <irogers@google.com>,
	Kees Cook <keescook@chromium.org>,
	sandipan.das@amd.com, Bill Wendling <morbo@google.com>,
	clang-built-linux <llvm@lists.linux.dev>,
	Yonghong Song <yhs@fb.com>, Peter Zijlstra <peterz@infradead.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: Invalid event (cycles:pp) in per-thread mode, enable system wide with '-a'.
Date: Tue, 11 Jul 2023 10:44:52 +0530	[thread overview]
Message-ID: <5acc07fe-d161-2977-29ab-1096afeefc4c@amd.com> (raw)
In-Reply-To: <CAKwvOdm9SAQ5i74JUzWP4Q1WW3aHq+3Jo7hqfie+oMxjnKqxSA@mail.gmail.com>

On 11-Jul-23 2:52 AM, Nick Desaulniers wrote:
> On Sun, Jun 25, 2023 at 10:45 PM Ravi Bangoria <ravi.bangoria@amd.com> wrote:
>>
>> Hi Nick,
>>
>> On 23-Jun-23 9:53 PM, Nick Desaulniers wrote:
>>>>> On 12-Oct-22 3:02 AM, Nick Desaulniers wrote:
>>> Hi Ravi,
>>> Sorry, I'm not able to load a custom kernel image on my employer
>>> provided workstation, and I never got approval to expense hardware for
>>> testing this otherwise.
>>>
>>> Was there ever any update on this? I'm on 6.1.25 now and still cant run
>>> $ perf record -e cycles:pp --call-graph lbr <any command to profile>
>>
>> Per-process precise sampling on AMD platforms should work from 6.2-rc1
>> onward.
> 
> Ok, I can wait for my employer to ship 6.2 on our workstations.
> 
>> However, --call-graph=lbr is not supported on AMD (hw limitation).
> 
> On any AMD uarches? Is there an equivalent? LBR encoding is compact
> which makes working it much faster than DWARF or stack frame
> unwinding.

I understand that LBR call-stack is the fastest option but unfortunately
none of the current AMD uarch supports it.

Thanks,
Ravi

  reply	other threads:[~2023-07-11  5:16 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
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 [this message]
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=5acc07fe-d161-2977-29ab-1096afeefc4c@amd.com \
    --to=ravi.bangoria@amd.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=namhyung@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    --cc=sandipan.das@amd.com \
    --cc=srw@sladewatkins.net \
    --cc=yhs@fb.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).