From: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>
To: Alison Wang <alison.wang@nxp.com>,
catalin.marinas@arm.com, will@kernel.org, paulmck@kernel.org,
mw@semihalf.com, leoyang.li@nxp.com, vladimir.oltean@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
alison.wang@nxp.com,
Anna-Maria Gleixner <anna-maria@linutronix.de>
Subject: Re: [RFC PATCH] arm64: defconfig: Disable fine-grained task level IRQ time accounting
Date: Wed, 29 Jul 2020 10:40:29 +0200 [thread overview]
Message-ID: <877dumbtoi.fsf@kurt> (raw)
In-Reply-To: <20200729033934.22349-1-alison.wang@nxp.com>
[-- Attachment #1.1: Type: text/plain, Size: 699 bytes --]
Hi Alison,
On Wed Jul 29 2020, Alison Wang wrote:
> In the current arm64 defconfig, CONFIG_IRQ_TIME_ACCOUNTING is enabled as
> default. According to my tests on NXP's LayerScape and i.MX platforms,
> the system hangs when running the command "stress-ng --hrtimers 1" with
> CONFIG_IRQ_TIME_ACCOUNTING enabled. Disabling this option, the issue
> disappears. CONFIG_IRQ_TIME_ACCOUNTING causes serious performance impact
> when running hrtimer stress test at the same time.
I think instead of disabling the option for all arm64 devices, it might
be better to analyze the root-cause why the hrtimer test hangs when this
option is enabled.
+Cc hrtimer maintainers: Thomas and Anna-Maria
Thanks,
Kurt
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-29 8:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 3:39 [RFC PATCH] arm64: defconfig: Disable fine-grained task level IRQ time accounting Alison Wang
2020-07-29 8:40 ` Kurt Kanzenbach [this message]
2020-07-29 8:50 ` [EXT] " Alison Wang
2020-07-29 9:49 ` Vladimir Oltean
2020-07-30 7:23 ` Kurt Kanzenbach
2020-07-30 8:22 ` Vladimir Oltean
2020-08-03 8:04 ` Kurt Kanzenbach
2020-08-03 8:16 ` Vladimir Oltean
2020-08-03 9:51 ` Robin Murphy
2020-08-03 11:38 ` Vladimir Oltean
2020-08-03 11:48 ` Valentin Schneider
2020-08-03 13:24 ` Marc Zyngier
2020-08-03 10:02 ` Thomas Gleixner
2020-08-03 10:49 ` Thomas Gleixner
2020-08-03 11:41 ` Vladimir Oltean
2020-08-03 15:13 ` Thomas Gleixner
2020-08-03 15:47 ` Valentin Schneider
2020-08-03 16:14 ` Vladimir Oltean
2020-08-03 19:22 ` Thomas Gleixner
2020-08-03 23:59 ` Valentin Schneider
2020-08-05 8:50 ` Dietmar Eggemann
2020-08-05 13:40 ` peterz
2020-08-05 13:56 ` Valentin Schneider
2020-08-05 15:31 ` peterz
2020-08-06 9:41 ` Thomas Gleixner
2020-08-06 11:45 ` peterz
2020-08-06 13:27 ` Paul E. McKenney
2020-08-06 19:03 ` Thomas Gleixner
2020-08-06 20:39 ` Paul E. McKenney
2020-08-06 18:58 ` Thomas Gleixner
2020-08-06 9:34 ` Thomas Gleixner
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=877dumbtoi.fsf@kurt \
--to=kurt.kanzenbach@linutronix.de \
--cc=alison.wang@nxp.com \
--cc=anna-maria@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
--cc=vladimir.oltean@nxp.com \
--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;
as well as URLs for NNTP newsgroup(s).