From: wangxiaolei <xiaolei.wang@windriver.com>
To: will@kernel.org, mark.rutland@arm.com, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@kernel.org, irogers@google.com, linux@armlinux.org.uk
Cc: linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: perf record -e branch-misses ls > /dev/null
Date: Wed, 8 Mar 2023 15:56:41 +0800 [thread overview]
Message-ID: <08994540-d132-6e49-f6a0-82d8dfd1f3f0@windriver.com> (raw)
hi
When I use the perf tool on nxp-imx6sx, the CPU is armv7 cortex-A9 to
test, I execute the perf record -e branch-misses ls > /dev/null command,
but the perf report result is indeed:
perf report
Error:
The perf.data data has no samples!
# To display the perf.data header info, please use
--header/--header-only options.
root@nxp-imx6:~# perf list hardware
List of pre-defined events (to be used in -e):
branch-instructions OR branches [Hardware event]
branch-misses [Hardware event]
bus-cycles [Hardware event]
cache-misses [Hardware event]
cache-references [Hardware event]
cpu-cycles OR cycles [Hardware event]
instructions [Hardware event]
And not only this one hardware event, only cycles are working normally
in the following supported hardware time, other hardware events are not
interrupted and reported, and the value in the read PMXEVCNTR register
is always -1, and the PMCR register E, bit[0 ] it will be written to 0
before reading the PMXEVCNTR register. I don’t know if the value in the
PMXEVCNTR register is always -1 for this reason. Does anyone have any
good suggestions for debugging this problem?
thanks
xiaolei
next reply other threads:[~2023-03-08 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 7:56 wangxiaolei [this message]
2023-03-23 17:51 ` Mark Rutland
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=08994540-d132-6e49-f6a0-82d8dfd1f3f0@windriver.com \
--to=xiaolei.wang@windriver.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.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=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®