From: Gerald BAEZA <gerald.baeza@st.com>
To: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"jolsa@redhat.com" <jolsa@redhat.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>
Cc: Alexandre TORGUE <alexandre.torgue@st.com>
Subject: perf tool issue following 'perf stat: Fix --no-scale' patch integration
Date: Wed, 21 Aug 2019 14:58:46 +0000 [thread overview]
Message-ID: <2680dc183a9e45b999be4939cbe67b44@SFHDAG5NODE1.st.com> (raw)
Dear Andi and all perf tool / arm debug experts
This is about the following patch :
perf stat: Fix --no-scale
SHA-1 : 75998bb263bf48c1c85d78cd2d2f3a97d3747cab
Since it is applied in the kernel, I noticed that perf tool fails on my ARMv7 platform (STM32MP1 with Cortex-A7 and NEON) with the following error :
root@stm32mp1:~# perf stat --no-scale sleep 1
[10827.350202] Alignment trap: perf (631) PC=0x001139e8 Instr=0xf4640adf Address=0x0021a804 1
[10827.357704] Alignment trap: not handling instruction f4640adf at [<001139e8>]
[10827.364867] 8<--- cut here ---
[10827.367875] Unhandled fault: alignment exception (0x001) at 0x0021a804
[10827.374427] pgd = 8abc1568
[10827.377090] [0021a804] *pgd=ff2e8835
Bus error
The same error happens with or without the --no-scale option.
This is to give the context. I do not blame your patch, Andi :)
I analyzed the root cause of this issue, summarized below, but then I need your lights to imagine the best correction.
One of the changes in the patch concerns tools/perf/util/stat.c :
case AGGR_GLOBAL:
aggr->val += count->val;
- if (config->scale) {
- aggr->ena += count->ena;
- aggr->run += count->run;
- }
+ aggr->ena += count->ena;
+ aggr->run += count->run;
The consequence of this new writing is that GCC generates a NEON vectored instruction to load count->val and count->ena values in 64 bits registers, since they are sequential in memory and systematically initialized now:
f4640adf vld1.64 {d16-d17}, [r4 :64]
The problem comes from the ':64' specifying that the parameter has to be 8 bytes aligned.
The 'count' pointer points inside the 'contents[]' array from the 'struct xyarray'.
If I force this field to be 64 bits aligned, then perf works again:
struct xyarray {
size_t row_size;
size_t entry_size;
size_t entries;
size_t max_x;
size_t max_y;
- char contents[] ;
+ char contents[] __attribute__((aligned(64)));
};
But the xyarray structure is generic so I think this patch cannot be the final one.
Some GCC versions have a -mgeneral-regs-only option to forbid the generation of NEON instructions while compiling one file, but this does not seem to be mainlined (?).
Well, I am hesitating and don't know what kind of correction I should apply.
I also don't know very well perf tool source code, so this sets some borders to my imagination :)
Can you help me please ?
Best regards
Gérald
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-08-21 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 14:58 Gerald BAEZA [this message]
[not found] <f686372a96ea490785c0a76cc96b3434@SFHDAG5NODE1.st.com>
[not found] ` <20190821162635.GB36669@tassilo.jf.intel.com>
[not found] ` <20190821195451.GG3929@kernel.org>
2019-08-22 7:17 ` perf tool issue following 'perf stat: Fix --no-scale' patch integration Gerald BAEZA
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=2680dc183a9e45b999be4939cbe67b44@SFHDAG5NODE1.st.com \
--to=gerald.baeza@st.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@st.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.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