From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: Nicolas Pitre <nico@cam.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] Orion NAND: Make dword load asm volatile to avoid GCC optimizing it away
Date: Fri, 21 Aug 2009 08:07:53 +0200 [thread overview]
Message-ID: <20090821080753.5a8be5c8@marrow.netinsight.se> (raw)
In-Reply-To: <alpine.LFD.2.00.0908201204320.6044@xanadu.home>
On Thu, 20 Aug 2009 12:14:47 -0400 (EDT)
Nicolas Pitre <nico@cam.org> wrote:
> > Yes, it works fine with 4.3.3 and 4.4.1 with this change. So the
> > updated patch can be found below. I belive the early clobber should be
> > there though, since (from the ARM architecture reference manual):
> >
> > If <addressing_mode> performs base register write-back and the base
> > register <Rn> is one of the two destination registers of the
> > instruction, the results are UNPREDICTABLE.
> >
> > it works fine without the early clobber as well, but I'd feel more safe
> > having it in.
>
> But this isn't the case here. We don't perform any writeback.
> You get a writeback when you have an addressing mode of the form:
>
> insn rd, [rn, rm]!
> insn rd, [rn, #off]!
> insn rd, [rn], #off
>
> but not with:
>
> insn rd, [rn, #off]
OK, I'm still a beginner on the ARM architecture, so thanks for the
explanation!
> Still the early clobber shouldn't have any adverse effect either, unlike
> the memory clobber.
>
> Acked-by: Nicolas Pitre <nico@marvell.com>
>
> Unless the MTD guys are going to pick this patch and push it to Linus
> soon I'll carry it in the Orion git repo.
Great, thanks!
// Simon
prev parent reply other threads:[~2009-08-21 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 14:41 [PATCH] Orion NAND: Make dword load asm volatile to avoid GCC optimizing it away Simon Kagstrom
2009-07-14 16:40 ` Nicolas Pitre
2009-08-19 7:45 ` Simon Kagstrom
2009-08-19 14:47 ` Nicolas Pitre
2009-08-20 7:19 ` Simon Kagstrom
2009-08-20 16:14 ` Nicolas Pitre
2009-08-21 6:07 ` Simon Kagstrom [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=20090821080753.5a8be5c8@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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