From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
tee-dev@lists.linaro.org, netdev@vger.kernel.org
Cc: vikas.gupta@broadcom.com, jakub.kicinski@netronome.com,
sheetal.tigadoli@broadcom.com, davem@davemloft.net,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: 5.5-rc1 regression with BNXT firmware driver
Date: Tue, 24 Dec 2019 14:03:35 +0000 [thread overview]
Message-ID: <86d05f68-e644-8b05-3154-4658813e986e@arm.com> (raw)
Hi,
I've been hunting down some hackbench regression between 5.4-rc8 and 5.5-rc1
on my Juno r0, one of the offenders seems to be:
246880958ac9 ("firmware: broadcom: add OP-TEE based BNXT f/w manager")
This is tested on a kernel built with defconfig (TEE_BNXT_FW gets selected)
and with:
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
./perf stat --null --sync --repeat 200 ./hackbench
The regression is easily reproducible on my end, this is 3 runs of the above
comparing the patch and its parent:
-PATCH:
0.71062 +- 0.00150 seconds time elapsed ( +- 0.21% )
0.71121 +- 0.00181 seconds time elapsed ( +- 0.25% )
0.71277 +- 0.00181 seconds time elapsed ( +- 0.25% )
+PATCH:
0.72556 +- 0.00174 seconds time elapsed ( +- 0.24% )
0.72695 +- 0.00192 seconds time elapsed ( +- 0.26% )
0.72559 +- 0.00178 seconds time elapsed ( +- 0.25% )
AIUI Vincent found something different while hunting down a similar
regression:
df323337e507 ("apparmor: Use a memory pool instead per-CPU caches")
but it seems this one is another cause. Seeing as this involves security
stuff the overhead may be acceptable, nevertheless now that I have some
reproducer I figured I'd send this out.
Cheers,
Valentin
reply other threads:[~2019-12-24 14:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=86d05f68-e644-8b05-3154-4658813e986e@arm.com \
--to=valentin.schneider@arm.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sheetal.tigadoli@broadcom.com \
--cc=tee-dev@lists.linaro.org \
--cc=vikas.gupta@broadcom.com \
--cc=vincent.guittot@linaro.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®