linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: L2 : Errata 588369: Clean & Invalidate do notinvalidate clean lines
Date: Mon, 11 Jan 2010 16:26:30 +0000	[thread overview]
Message-ID: <1263227190.6305.51.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20100111152333.GB4109@n2100.arm.linux.org.uk>

On Mon, 2010-01-11 at 15:23 +0000, Russell King - ARM Linux wrote:
> On Mon, Jan 11, 2010 at 08:48:37PM +0530, Shilimkar, Santosh wrote:
> > > Do you need to specify "r12" as well? What about "cc", are they
> > > preserved by the secure monitor?
> >
> > r12 and reset of the registers are preserved. Lr needs to be saved but
> > because of function call, the compiler saves/restores it.
> 
> That's not guaranteed; the compiler can re-use lr for its own purposes
> within a function.  You need to add lr to the list of clobbered registers.

Do we need to specify "r12" in the list of clobbered registers as the
inline asm explicitly modifies it? Or the compiler doesn't touch it.

-- 
Catalin

  parent reply	other threads:[~2010-01-11 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 10:09 [PATCH v3] ARM: L2 : Errata 588369: Clean & Invalidate do not invalidate clean lines Santosh Shilimkar
2010-01-07  7:44 ` Shilimkar, Santosh
2010-01-11 14:37 ` Catalin Marinas
2010-01-11 14:45   ` Russell King - ARM Linux
2010-01-11 15:21     ` Shilimkar, Santosh
2010-01-11 15:18   ` Shilimkar, Santosh
2010-01-11 15:23     ` Russell King - ARM Linux
2010-01-11 15:29       ` Shilimkar, Santosh
2010-01-12  7:41         ` Shilimkar, Santosh
2010-01-11 16:26       ` Catalin Marinas [this message]
2010-01-11 16:29         ` [PATCH v3] ARM: L2 : Errata 588369: Clean & Invalidate do notinvalidate " 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=1263227190.6305.51.camel@pc1117.cambridge.arm.com \
    --to=catalin.marinas@arm.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).