From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: James Clark <james.clark@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Anshuman.Khandual@arm.com, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Kajol Jain <kjain@linux.ibm.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf test: Fix skipping branch stack sampling test
Date: Tue, 8 Nov 2022 18:00:54 -0300 [thread overview]
Message-ID: <Y2rDhkyn9ta5skDm@kernel.org> (raw)
In-Reply-To: <F79AE69A-4D87-4F4E-A3FD-EF06A6E12839@linux.vnet.ibm.com>
Em Wed, Nov 02, 2022 at 12:21:11PM +0530, Athira Rajeev escreveu:
>
>
> > On 28-Oct-2022, at 5:52 PM, James Clark <james.clark@arm.com> wrote:
> >
> >
> >
> > On 28/10/2022 13:19, James Clark wrote:
> >> Commit f4a2aade6809 ("perf tests powerpc: Fix branch stack sampling test
> >> to include sanity check for branch filter") added a skip if certain
> >> branch options aren't available. But the change added both -b
> >> (--branch-any) and --branch-filter options at the same time, which will
> >> always result in a failure on any platform because the arguments can't
> >> be used together.
> >>
> >> Fix this by removing -b (--branch-any) and leaving --branch-filter which
> >> already specifies 'any'. Also add warning messages to the test and perf
> >> tool.
> >>
> >
> > Hi Athira,
> >
> > Are you able to check if this still skips for you on PowerPC with this
> > new change?
> >
>
> Hi James,
>
> Sorry for the late response. I was out on vacation couple of days.
>
> I tested with the new change and verified it skips on powerpc.
>
> Tested-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Thanks, applied.
- Arnaldo
> Thanks
> Athira
> > Thanks
> > James
> >
> >> Output on x86 before this fix:
> >>
> >> $ sudo ./perf test branch
> >> 108: Check branch stack sampling : Skip
> >>
> >> After:
> >>
> >> $ sudo ./perf test branch
> >> 108: Check branch stack sampling : Ok
> >>
> >> Fixes: f4a2aade6809 ("perf tests powerpc: Fix branch stack sampling test to include sanity check for branch filter")
> >> Signed-off-by: James Clark <james.clark@arm.com>
> >> ---
> >> tools/perf/tests/shell/test_brstack.sh | 5 ++++-
> >> tools/perf/util/parse-branch-options.c | 4 +++-
> >> 2 files changed, 7 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/tools/perf/tests/shell/test_brstack.sh b/tools/perf/tests/shell/test_brstack.sh
> >> index ec801cffae6b..d7ff5c4b4da4 100755
> >> --- a/tools/perf/tests/shell/test_brstack.sh
> >> +++ b/tools/perf/tests/shell/test_brstack.sh
> >> @@ -13,7 +13,10 @@ fi
> >>
> >> # skip the test if the hardware doesn't support branch stack sampling
> >> # and if the architecture doesn't support filter types: any,save_type,u
> >> -perf record -b -o- -B --branch-filter any,save_type,u true > /dev/null 2>&1 || exit 2
> >> +if ! perf record -o- --no-buildid --branch-filter any,save_type,u -- true > /dev/null 2>&1 ; then
> >> + echo "skip: system doesn't support filter types: any,save_type,u"
> >> + exit 2
> >> +fi
> >>
> >> TMPDIR=$(mktemp -d /tmp/__perf_test.program.XXXXX)
> >>
> >> diff --git a/tools/perf/util/parse-branch-options.c b/tools/perf/util/parse-branch-options.c
> >> index 00588b9db474..31faf2bb49ff 100644
> >> --- a/tools/perf/util/parse-branch-options.c
> >> +++ b/tools/perf/util/parse-branch-options.c
> >> @@ -102,8 +102,10 @@ parse_branch_stack(const struct option *opt, const char *str, int unset)
> >> /*
> >> * cannot set it twice, -b + --branch-filter for instance
> >> */
> >> - if (*mode)
> >> + if (*mode) {
> >> + pr_err("Error: Can't use --branch-any (-b) with --branch-filter (-j).\n");
> >> return -1;
> >> + }
> >>
> >> return parse_branch_str(str, mode);
> >> }
--
- Arnaldo
prev parent reply other threads:[~2022-11-08 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 12:19 [PATCH] perf test: Fix skipping branch stack sampling test James Clark
2022-10-28 12:22 ` James Clark
2022-11-02 6:51 ` Athira Rajeev
2022-11-08 21:00 ` Arnaldo Carvalho de Melo [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=Y2rDhkyn9ta5skDm@kernel.org \
--to=acme@kernel.org \
--cc=Anshuman.Khandual@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--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@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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).