From: rogerq@ti.com (Roger Quadros)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: Do not run dummy_flush_tlb_a15_erratum() on non-Cortex-A15
Date: Tue, 23 Jul 2013 17:04:48 +0300 [thread overview]
Message-ID: <51EE8D80.8010409@ti.com> (raw)
In-Reply-To: <1374581199-8277-1-git-send-email-festevam@gmail.com>
On 07/23/2013 03:06 PM, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Commit 93dc688 (ARM: 7684/1: errata: Workaround for Cortex-A15 erratum 798181
> (TLBI/DSB operations)) causes the following undefined instruction error on a
> mx53 (Cortex-A8):
>
> Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
> CPU: 0 PID: 275 Comm: modprobe Not tainted 3.11.0-rc2-next-20130722-00009-g9b0f371 #881
> task: df46cc00 ti: df48e000 task.ti: df48e000
> PC is at check_and_switch_context+0x17c/0x4d0
> LR is at check_and_switch_context+0xdc/0x4d0
>
> This problem happens because check_and_switch_context() calls
> dummy_flush_tlb_a15_erratum() without checking if we are really running on a
> Cortex-A15 or not.
>
> To avoid this issue, only call dummy_flush_tlb_a15_erratum() inside
> check_and_switch_context() if erratum_a15_798181() returns true, which means
> that we are really running on a Cortex-A15.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Reviewed-by: Roger Quadros <rogerq@ti.com>
next prev parent reply other threads:[~2013-07-23 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 12:06 [PATCH v2] ARM: Do not run dummy_flush_tlb_a15_erratum() on non-Cortex-A15 Fabio Estevam
2013-07-23 13:08 ` Catalin Marinas
2013-07-23 14:04 ` Roger Quadros [this message]
2013-07-24 17:00 ` Paul Walmsley
2013-08-01 4:03 ` Rob Herring
2013-08-01 10:58 ` Russell King - ARM Linux
2013-08-01 20:09 ` Rob Herring
2013-08-01 20:15 ` Russell King - ARM Linux
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=51EE8D80.8010409@ti.com \
--to=rogerq@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.