From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
Rajendra Nayak <rnayak@codeaurora.org>,
Will Deacon <will.deacon@arm.com>, Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: avoid Cortex-A9 livelock on tight dmb loops
Date: Sun, 15 Apr 2018 16:50:37 +0100 [thread overview]
Message-ID: <20180415155037.GI10990@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20180415140833.GH10990@n2100.armlinux.org.uk>
On Sun, Apr 15, 2018 at 03:08:34PM +0100, Russell King - ARM Linux wrote:
> On Wed, Apr 11, 2018 at 07:11:39AM -0700, Tony Lindgren wrote:
> > We already have code in the kernel (and in the bootrom) to "park" a
> > cpu after starting. But using it without resetting the cpu would require
> > 1-1 memory mapping or modifying the code. That is if we wanted to use
> > the same code also for parking the cpus for kexec without resetting
> > them.
>
> In which case, how about using:
>
> while (1) {
> cpu_relax();
> wfe();
> }
>
> instead - that appears to also have the desired effect, allowing kdump
> to work on the SDP4430.
... but results in compile failures on non-ARMv7 targets.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
prev parent reply other threads:[~2018-04-15 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 10:41 [PATCH] ARM: avoid Cortex-A9 livelock on tight dmb loops Russell King
2018-04-10 13:41 ` Tony Lindgren
2018-04-10 14:12 ` Tero Kristo
2018-04-10 15:28 ` Will Deacon
2018-04-11 12:52 ` Russell King - ARM Linux
2018-04-11 12:57 ` Tero Kristo
2018-04-11 12:59 ` Keerthy
2018-04-11 13:10 ` Russell King - ARM Linux
2018-04-11 14:11 ` Tony Lindgren
2018-04-15 14:08 ` Russell King - ARM Linux
2018-04-15 15:50 ` Russell King - ARM Linux [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=20180415155037.GI10990@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@codeaurora.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
--cc=will.deacon@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