From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM PJ4B: Add support for errata 4742
Date: Tue, 04 Jun 2013 19:19:35 +0200 [thread overview]
Message-ID: <51AE21A7.5080907@free-electrons.com> (raw)
In-Reply-To: <20130604145958.GY18614@n2100.arm.linux.org.uk>
Dear Russell King,
On 06/04/2013 04:59 PM, Russell King - ARM Linux wrote:
> On Tue, Jun 04, 2013 at 04:03:17PM +0200, Gregory CLEMENT wrote:
>> From: Lior Amsalem <alior@marvell.com>
>>
>> This commit fixes the regression on Armada 370 (the kernal hang during
>> boot) introduced by the commit: "ARM: 7691/1: mm: kill unused
>> TLB_CAN_READ_FROM_L1_CACHE and use ALT_SMP instead".
>>
>> When coming out of either a Wait for Interrupt (WFI) or a Wait for
>> Event (WFE) IDLE states, a specific timing sensitivity exists between
>> the retiring WFI/WFE instructions and the newly issued subsequent
>> instructions. This sensitivity can result in a CPU hang scenario. The
>> workaround is to insert either a Data Synchronization Barrier (DSB) or
>> Data Memory Barrier (DMB) command immediately after the WFI/WFE
>> instruction
>
> Wouldn't a DMB be cheaper than a full blown DSB here?
I let Lior answer to this question.
>
> Also, we could detect the PJ4B and only implement the workaround
> on those CPUs rather than having to have it on every v7 CPU - which
> is important when you consider the single zImage issues.
At least we can detect the PJ4B and maybe even the detect the if it
is the PJ4B or the PJ4B-MP.
Do you mean to add this test in the cpu_v7_do_idle() function?
Or patching the pointer to the cpu_v7_do_idle() on the fly? In this
last case it seems a little tricky to me, as we should have to modify
a pointer function in the .proc.info.init section.
Thanks for your review,
Gregory
next prev parent reply other threads:[~2013-06-04 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 14:03 [PATCH v2 0/2] ARM: PJ4B: fixes for 3.10-rc Gregory CLEMENT
2013-06-04 14:03 ` [PATCH v2 1/2] ARM PJ4B: Add support for errata 4742 Gregory CLEMENT
2013-06-04 14:59 ` Russell King - ARM Linux
2013-06-04 17:19 ` Gregory CLEMENT [this message]
2013-06-04 17:35 ` Will Deacon
2013-06-04 17:37 ` Russell King - ARM Linux
2013-06-04 18:07 ` Nicolas Pitre
2013-06-04 18:10 ` Russell King - ARM Linux
2013-06-04 18:19 ` Nicolas Pitre
2013-06-04 18:21 ` Russell King - ARM Linux
2013-06-04 18:32 ` Nicolas Pitre
2013-06-04 19:04 ` Gregory CLEMENT
2013-06-04 14:03 ` [PATCH v2 2/2] ARM PJ4B: Add support for errata 4611 Gregory CLEMENT
2013-06-04 15:41 ` Will Deacon
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=51AE21A7.5080907@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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