From: Namhyung Kim <namhyung@kernel.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
James Clark <james.clark@arm.com>,
Kajol Jain <kjain@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Atish Patra <atishp@atishpatra.org>,
Palmer Dabbelt <palmer@rivosinc.com>,
Mingwei Zhang <mizhang@google.com>
Subject: Re: [PATCH 7/8] perf tools: Check fallback error and order
Date: Tue, 15 Oct 2024 21:33:47 -0700 [thread overview]
Message-ID: <Zw9CK2mS6fHoxnKf@google.com> (raw)
In-Reply-To: <bbffa9eb-0102-4c35-8b1a-4e26634aa878@amd.com>
Hello Ravi,
On Tue, Oct 15, 2024 at 09:51:50AM +0530, Ravi Bangoria wrote:
> > @@ -2366,9 +2403,6 @@ static int evsel__open_cpu(struct evsel *evsel, struct perf_cpu_map *cpus,
> > return 0;
> >
> > try_fallback:
> > - if (evsel__precise_ip_fallback(evsel))
> > - goto retry_open;
> > -
> > if (evsel__ignore_missing_thread(evsel, perf_cpu_map__nr(cpus),
> > idx, threads, thread, err)) {
> > /* We just removed 1 thread, so lower the upper nthreads limit. */
> > @@ -2385,11 +2419,15 @@ static int evsel__open_cpu(struct evsel *evsel, struct perf_cpu_map *cpus,
> > if (err == -EMFILE && rlimit__increase_nofile(&set_rlimit))
> > goto retry_open;
> >
> > - if (err != -EINVAL || idx > 0 || thread > 0)
> > - goto out_close;
> > + if (err == -EOPNOTSUPP && evsel__precise_ip_fallback(evsel))
> > + goto retry_open;
>
> This will change the behavior of events like instructions:P on AMD.
>
> Without patch:
> $ ./perf record -e instructions:P -- true
> [ perf record: Woken up 2 times to write data ]
> [ perf record: Captured and wrote 0.009 MB perf.data (9 samples) ]
>
> With the patch:
>
> $ ./perf record -e instructions:P -- true
> Error:
> The instructions:Pu event is not supported.
Thanks for the test, it should support other events too. I've noticed
it returns -ENOENT for non-IBS events with precise_ip > 0. Will handle
them as well.
Thanks,
Namhyung
next prev parent reply other threads:[~2024-10-16 4:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 0:20 [PATCHSET 0/8] perf tools: Do not set attr.exclude_guest by default (v4) Namhyung Kim
2024-10-01 0:20 ` [PATCH 1/8] perf tools: Add fallback for exclude_guest Namhyung Kim
2024-10-01 17:41 ` Ian Rogers
2024-10-01 0:20 ` [PATCH 2/8] perf tools: Don't set attr.exclude_guest by default Namhyung Kim
2024-10-01 17:43 ` Ian Rogers
2024-10-01 0:20 ` [PATCH 3/8] perf tools: Simplify evsel__add_modifier() Namhyung Kim
2024-10-01 17:44 ` Ian Rogers
2024-10-01 0:20 ` [PATCH 4/8] perf tools: Do not set exclude_guest for precise_ip Namhyung Kim
2024-10-01 17:46 ` Ian Rogers
2024-10-01 0:20 ` [PATCH 5/8] perf tools: Detect missing kernel features properly Namhyung Kim
2024-10-01 17:53 ` Ian Rogers
2024-10-01 21:32 ` Namhyung Kim
2024-10-15 4:19 ` Ravi Bangoria
2024-10-16 4:49 ` Namhyung Kim
2024-10-01 0:20 ` [PATCH 6/8] perf tools: Move x86__is_amd_cpu() to util/env.c Namhyung Kim
2024-10-01 16:03 ` Liang, Kan
2024-10-01 22:39 ` Namhyung Kim
2024-10-01 0:20 ` [PATCH 7/8] perf tools: Check fallback error and order Namhyung Kim
2024-10-01 18:00 ` Ian Rogers
2024-10-01 21:36 ` Namhyung Kim
2024-10-01 22:21 ` Ian Rogers
2024-10-03 17:06 ` Namhyung Kim
2024-10-03 17:32 ` Ian Rogers
2024-10-03 22:38 ` Namhyung Kim
2024-10-14 19:22 ` Namhyung Kim
2024-10-15 4:21 ` Ravi Bangoria
2024-10-16 4:33 ` Namhyung Kim [this message]
2024-10-16 4:47 ` Ian Rogers
2024-10-01 0:20 ` [PATCH 8/8] perf record: Just use "cycles:P" as the default event Namhyung Kim
2024-10-01 18:00 ` Ian Rogers
2024-10-01 17:46 ` [PATCHSET 0/8] perf tools: Do not set attr.exclude_guest by default (v4) Liang, Kan
2024-10-01 21:19 ` Namhyung Kim
2024-10-02 9:49 ` James Clark
2024-10-02 18:29 ` Namhyung Kim
2024-10-04 15:40 ` James Clark
2024-10-04 19:17 ` Namhyung Kim
2024-10-15 4:25 ` Ravi Bangoria
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=Zw9CK2mS6fHoxnKf@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=atishp@atishpatra.org \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mizhang@google.com \
--cc=palmer@rivosinc.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=tmricht@linux.ibm.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