linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 7 Mar 2012 15:02:42 +0530	[thread overview]
Message-ID: <20120307093240.GA21265@bnru02> (raw)
In-Reply-To: <20120117133428.GB11581@mudshark.cambridge.arm.com>

On Tue, Jan 17, 2012 at 14:34:28 +0100, Will Deacon wrote:
> On Tue, Jan 17, 2012 at 11:27:43AM +0000, Srinidhi KASAGAR wrote:
> > On Tue, Jan 17, 2012 at 11:30:23 +0100, Will Deacon wrote:
> > > On Tue, Jan 17, 2012 at 06:22:26AM +0000, Srinidhi KASAGAR wrote:
> > > > 
> > > > Yes, we boot with L2 enabled.
> > > 
> > > Interesting. I'm surprised you don't have problems with stale data on the
> > > D-side after the decompressor. Maybe you're lucky with the mappings being no
> > > write allocate.
> > 
> > Actually the pre bootloader makes sure that L2 is clean before relinquishing
> > the control to kernel decompressor.
> 
> I was thinking more of the decompressor populating the L2 and not flushing
> it.

Perhaps, we are lucky because we lock down l2 in bootloader?

srinidhi

      parent reply	other threads:[~2012-03-07  9:32 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
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 [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=20120307093240.GA21265@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).