From: Namhyung Kim <namhyung@kernel.org>
To: Veronika Molnarova <vmolnaro@redhat.com>
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org,
acme@redhat.com, kjain@linux.ibm.com, mpetlan@redhat.com,
rstoyano@redhat.com, mark.rutland@arm.com, jolsa@kernel.org,
alexander.shishkin@linux.intel.com, adrian.hunter@intel.com
Subject: Re: [PATCH v4] perf test stat_all_pmu.sh: Parse return value of perf stat
Date: Tue, 1 Oct 2024 18:22:47 -0700 [thread overview]
Message-ID: <ZvygZ4GQIusndmOu@google.com> (raw)
In-Reply-To: <ZvyTE4x9-BxCVx5J@google.com>
On Tue, Oct 01, 2024 at 05:25:55PM -0700, Namhyung Kim wrote:
> On Tue, Oct 01, 2024 at 10:35:33AM +0200, Veronika Molnarova wrote:
> >
> >
> > On 8/14/24 19:01, vmolnaro@redhat.com wrote:
> > > From: Veronika Molnarova <vmolnaro@redhat.com>
> > >
> > > With the upstream MR !3916 of commit ad86d7ee43b22aa2 ('powerpc/hv-gpci:
> > > Fix the H_GET_PERF_COUNTER_INFO hcall return value checks') the perf
> > > stat for hv_gpci events without required permission set returns an
> > > error value of -1 to differentiate the output from the unsupported
> > > events. The stat_all_pmu test was designed in a way, that if any
> > > command exits with a non-zero value the test exits with an error
> > > value without any information provided due to the 'set -e' option.
> > >
> > > The issue propagated upstream as the list of the files that affected perf
> > > did not cover the changed files and was updated after the issue was
> > > discovered. It was caught by CKI testing where it was triaged to stop
> > > blocking further MRs, as most of the powerpc machines have some of
> > > the hv_gpci events without the required permissions.
> > >
> > > Remove the 'set -e' option from the test and rework the test case to log
> > > the status of the event for better maintainability. Instead of exiting
> > > immediately after 'perf stat' ends with a non-zero value, check the
> > > return value and output of the 'perf stat' command with the appropriate action.
> > >
> > > Link to the MR !3916 of commit ad86d7ee43b22aa2:
> > > https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/3916
> > >
> > > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > > Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > > Cc: Jiri Olsa <jolsa@kernel.org>
> > > Cc: Mark Rutland <mark.rutland@arm.com>
> > > Cc: Michael Petlan <mpetlan@redhat.com>
> > > Cc: Radostin Stoyanov <rstoyano@redhat.com>
> > > Signed-off-by: Veronika Molnarova <vmolnaro@redhat.com>
Also, please collect reviewers' tags in the previous versions like
Reviewed-by and Tested-by from Kajol Jain.
Thanks,
Namhyung
prev parent reply other threads:[~2024-10-02 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 17:01 [PATCH v4] perf test stat_all_pmu.sh: Parse return value of perf stat vmolnaro
2024-10-01 8:35 ` Veronika Molnarova
2024-10-02 0:25 ` Namhyung Kim
2024-10-02 1:22 ` 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=ZvygZ4GQIusndmOu@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mpetlan@redhat.com \
--cc=rstoyano@redhat.com \
--cc=vmolnaro@redhat.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).