From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: Yicong Yang <yangyicong@huawei.com>,
linux-arm-kernel@lists.infradead.org, yangyicong@hisilicon.com,
linuxarm@huawei.com, prime.zeng@hisilicon.com,
mark.rutland@arm.com, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@kernel.org, yao.jin@linux.intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Fix auto-complete on aarch64
Date: Wed, 8 Feb 2023 10:39:16 -0300 [thread overview]
Message-ID: <Y+OmBGCL3DyKd28V@kernel.org> (raw)
In-Reply-To: <0ded9983-8a37-d6c9-3de8-cbde6a4ce1e7@arm.com>
Em Wed, Feb 08, 2023 at 10:35:17AM +0000, James Clark escreveu:
>
>
> On 07/02/2023 03:50, Yicong Yang wrote:
> > From: Yicong Yang <yangyicong@hisilicon.com>
> >
> > On aarch64 CPU related events are not under event_source/devices/cpu/events,
> > they're under event_source/devices/armv8_pmuv3_0/events on my machine.
> > Using current auto-complete script will generate below error:
> >
> > [root@localhost bin]# perf stat -e
> > ls: cannot access '/sys/bus/event_source/devices/cpu/events': No such file or directory
> >
> > Fix this by not test /sys/bus/event_source/devices/cpu/events on aarch64
> > machine.
> >
> > Fixes: 74cd5815d9af ("perf tool: Improve bash command line auto-complete for multiple events with comma")
> > Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
> > ---
> > tools/perf/perf-completion.sh | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
> >
>
> Reviewed-by: James Clark <james.clark@arm.com>
Thanks, applied.
- Arnaldo
> > diff --git a/tools/perf/perf-completion.sh b/tools/perf/perf-completion.sh
> > index fdf75d45efff..978249d7868c 100644
> > --- a/tools/perf/perf-completion.sh
> > +++ b/tools/perf/perf-completion.sh
> > @@ -165,7 +165,12 @@ __perf_main ()
> >
> > local cur1=${COMP_WORDS[COMP_CWORD]}
> > local raw_evts=$($cmd list --raw-dump)
> > - local arr s tmp result
> > + local arr s tmp result cpu_evts
> > +
> > + # aarch64 doesn't have /sys/bus/event_source/devices/cpu/events
> > + if [[ `uname -m` != aarch64 ]]; then
> > + cpu_evts=$(ls /sys/bus/event_source/devices/cpu/events)
> > + fi
> >
> > if [[ "$cur1" == */* && ${cur1#*/} =~ ^[A-Z] ]]; then
> > OLD_IFS="$IFS"
> > @@ -183,9 +188,9 @@ __perf_main ()
> > fi
> > done
> >
> > - evts=${result}" "$(ls /sys/bus/event_source/devices/cpu/events)
> > + evts=${result}" "${cpu_evts}
> > else
> > - evts=${raw_evts}" "$(ls /sys/bus/event_source/devices/cpu/events)
> > + evts=${raw_evts}" "${cpu_evts}
> > fi
> >
> > if [[ "$cur1" == , ]]; then
--
- Arnaldo
prev parent reply other threads:[~2023-02-08 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 3:50 [PATCH] perf tools: Fix auto-complete on aarch64 Yicong Yang
2023-02-08 10:35 ` James Clark
2023-02-08 13:39 ` 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=Y+OmBGCL3DyKd28V@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=prime.zeng@hisilicon.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.com \
--cc=yao.jin@linux.intel.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).