From: srinidhi.kasagar@stericsson.com (Srinidhi KASAGAR)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mach-ux500: cache operations are atomic on PL310
Date: Mon, 16 Jan 2012 16:35:29 +0530 [thread overview]
Message-ID: <20120116110528.GA24824@bnru02> (raw)
In-Reply-To: <20120113181422.GB24373@mudshark.cambridge.arm.com>
On Fri, Jan 13, 2012 at 19:14:22 +0100, Will Deacon wrote:
> Hi guys,
>
> On Thu, Jan 12, 2012 at 05:37:42AM +0000, Srinidhi KASAGAR wrote:
> > Apply ERRATA_753970 for ux500 variant of cache sync too
> >
> > Signed-off-by: srinidhi kasagar <srinidhi.kasagar@stericsson.com>
> > Acked-by: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > arch/arm/mach-ux500/cache-l2x0.c | 11 ++++++++---
> > 1 files changed, 8 insertions(+), 3 deletions(-)
>
> I hadn't noticed the existence of this file before, but this patch really
> shows why it's not a good idea to copy files out of core ARM code and into
> the mach-* directories. I see that the commit introducing this file 458eef2f
> ("mach-ux500: factor out l2x0 handling code") mentions that mach-imx does
> the same thing, but I can't find the code there.
>
> On top of that, it seems as though you provide an inv_all implementation
> but your disable function is empty. Surely this can lead to data loss?
We can't disable l2x0 from non secure mode and either we do not have
special SMI to handle the same and hence it is empty. So for kexec
to work on this platform we need to have a non-locking variant of
inv_all() otherwise we seems to be looping forever in spin locks
as such L1 caches are disabled at that moment in cpu_proc_fin().
So we had to override this inv_all for this machine.
Otherwise, what do you suggest? Whats the effect if we remove
that spin lock in inv_all as such I don't see much users using
inv_all.
srinidhi
next prev parent reply other threads:[~2012-01-16 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 5:37 [PATCH 1/2] mach-ux500: cache operations are atomic on PL310 Srinidhi KASAGAR
2012-01-12 5:37 ` [PATCH 2/2] mach-ux500: enable ARM errata 764369 Srinidhi KASAGAR
2012-01-13 18:14 ` [PATCH 1/2] mach-ux500: cache operations are atomic on PL310 Will Deacon
2012-01-16 11:05 ` Srinidhi KASAGAR [this message]
2012-01-16 14:50 ` Will Deacon
2012-01-17 6:22 ` Srinidhi KASAGAR
2012-01-17 10:30 ` Will Deacon
2012-01-17 11:27 ` Srinidhi KASAGAR
2012-01-17 13:34 ` Will Deacon
2012-01-18 12:06 ` Linus Walleij
2012-03-07 9:32 ` Srinidhi Kasagar
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=20120116110528.GA24824@bnru02 \
--to=srinidhi.kasagar@stericsson.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;
as well as URLs for NNTP newsgroup(s).