From: Al Viro <viro@ZenIV.linux.org.uk>
To: Matt Turner <mattst88@gmail.com>
Cc: Will Deacon <will.deacon@arm.com>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [PATCH] alpha: spinlock: don't perform memory access in locked critical section
Date: Mon, 6 May 2013 21:53:30 +0100 [thread overview]
Message-ID: <20130506205329.GO25399@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAEdQ38HnWbUB=ZNCZeYz8GZH3U4bv_Uag8WL2zT0D=GMcoT+2A@mail.gmail.com>
On Mon, May 06, 2013 at 01:19:51PM -0700, Matt Turner wrote:
> I'm not sure of the interpretation that LDA counts as a memory access.
>
> The manual says it's Ra <- Rbv + SEXT(disp).
>
> It's not touching memory that I can see.
More to the point, the same manual gives explicit list of instructions
that shouldn't occur between LDx_L and STx_C, and LDA does not belong to any
of those. I suspect that Will has misparsed the notations in there - LDx is
present in the list, but it's _not_ "all instructions with mnemonics starting
with LD", just the 4 "load integer from memory" ones. FWIW, instructions
with that encoding (x01xxx<a:5><b:5><offs:16>) are grouped so:
LDAx - LDA, LDAH; load address
LDx - LDL, LDQ, LDBU, LDWU; load memory data into integer register
LDQ_U; load unaligned
LDx_L - LDL_L, LDQ_L; load locked
STx_C - STL_C, STQ_C; store conditional
STx - STL, STQ, STB, STW; store
STQ_U; store unaligned
They all have the same encoding, naturally enough (operation/register/address
representation), but that's it... See section 4.2 in reference manual for
details; relevant note follows discussion of LDx_L and it spells the list
out. LDx is present, LDAx isn't (and neither is LDA by itself).
next prev parent reply other threads:[~2013-05-06 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 20:01 [PATCH] alpha: spinlock: don't perform memory access in locked critical section Will Deacon
2013-05-06 20:19 ` Matt Turner
2013-05-06 20:53 ` Al Viro [this message]
2013-05-06 21:12 ` Will Deacon
2013-05-06 21:28 ` Måns Rullgård
2013-05-06 22:11 ` Will Deacon
2013-05-06 20:26 ` Al Viro
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=20130506205329.GO25399@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--cc=will.deacon@arm.com \
/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).