From: Namhyung Kim <namhyung@kernel•org>
To: Athira Rajeev <atrajeev@linux•ibm.com>
Cc: Ian Rogers <irogers@google•com>, Venkat <venkat88@linux•ibm.com>,
Thomas Falcon <thomas.falcon@intel•com>,
acme@kernel•org, jolsa@kernel•org, adrian.hunter@intel•com,
vmolnaro@redhat•com, mpetlan@redhat•com, tmricht@linux•ibm.com,
maddy@linux•ibm.com, linux-perf-users@vger•kernel.org,
linuxppc-dev@lists•ozlabs.org, hbathini@linux•vnet.ibm.com,
Tejas.Manhas1@ibm•com, Tanushree.Shah@ibm•com,
Shivani.Nittor@ibm•com
Subject: Re: [PATCH] tools/perf/test: Check for perf stat return code in perf all PMU test
Date: Thu, 2 Apr 2026 18:27:46 -0700 [thread overview]
Message-ID: <ac8Xkty-lqrIbFsP@google.com> (raw)
In-Reply-To: <A33EEA7D-DB03-4FA9-A0A8-D10115FEF423@linux.ibm.com>
On Thu, Apr 02, 2026 at 09:15:54PM +0530, Athira Rajeev wrote:
> If the addition of “-a” can cause regression ( like intel one if its not suppose to be run system wide ),
> how about adding a case like this:
> - Look for "enable system wide with '-a’ “ in the error logs
> - If logs matches this message and if user is root, attempt with -a next.
> - With “-a”, If the logs has "Operation not supported” , test can continue to next event.
Sounds good, you can check perf_event_paranoid as well as root. Then
you don't need to check the result of "-a" for -EOPNOTSUP.
Thanks,
Namhyung
next prev parent reply other threads:[~2026-04-03 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 10:57 [PATCH] tools/perf/test: Check for perf stat return code in perf all PMU test Athira Rajeev
2026-03-23 10:39 ` Venkat
2026-04-01 20:40 ` Ian Rogers
2026-04-01 23:48 ` Namhyung Kim
2026-04-01 23:57 ` Ian Rogers
2026-04-02 15:45 ` Athira Rajeev
2026-04-03 1:27 ` Namhyung Kim [this message]
2026-04-02 17:32 ` Falcon, Thomas
2026-04-03 7:36 ` Mi, Dapeng
2026-04-03 15:39 ` Ian Rogers
2026-04-07 0:48 ` Mi, Dapeng
2026-05-15 6:25 ` Mi, Dapeng
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=ac8Xkty-lqrIbFsP@google.com \
--to=namhyung@kernel$(echo .)org \
--cc=Shivani.Nittor@ibm$(echo .)com \
--cc=Tanushree.Shah@ibm$(echo .)com \
--cc=Tejas.Manhas1@ibm$(echo .)com \
--cc=acme@kernel$(echo .)org \
--cc=adrian.hunter@intel$(echo .)com \
--cc=atrajeev@linux$(echo .)ibm.com \
--cc=hbathini@linux$(echo .)vnet.ibm.com \
--cc=irogers@google$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=linux-perf-users@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mpetlan@redhat$(echo .)com \
--cc=thomas.falcon@intel$(echo .)com \
--cc=tmricht@linux$(echo .)ibm.com \
--cc=venkat88@linux$(echo .)ibm.com \
--cc=vmolnaro@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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