From: Richard Henderson <richard.henderson@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Ivan Kokshaysky <ink@unseen.parts>,
Matt Turner <mattst88@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Magnus Lindholm <linmag7@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Alpha: Emulate unaligned LDx_L/STx_C for data consistency
Date: Thu, 20 Feb 2025 10:12:02 -0800 [thread overview]
Message-ID: <dfb14748-c5b8-4a50-990b-d61765a6a75c@linaro.org> (raw)
In-Reply-To: <CAHk-=wj42Dks1vknzKKBbXUMCrs-iuLZHq=0z3P0AN9TrXNP+A@mail.gmail.com>
On 2/20/25 09:59, Linus Torvalds wrote:
> On Thu, 20 Feb 2025 at 09:54, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> Crucially, when emulating non-aligned, you should not strive to make it atomic. No other
>> architecture promises atomic non-aligned stores, so why should you do that here?
>
> I'm not disagreeing with the "it doesn't necessarily have to be
> atomic", but I will point out that x86 does indeed promise atomic
> non-aligned accesses.
I should have been more expansive with that statement: I didn't mean "no unaligned
atomics" (e.g. lock orw), but "unaligned normal stores may be non-atomic" (e.g. movw
across a cacheline).
My guess about the gcc patches is that it's the latter that wanted emulation here.
r~
next prev parent reply other threads:[~2025-02-20 18:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 12:46 Maciej W. Rozycki
2025-02-19 17:38 ` Magnus Lindholm
2025-02-19 23:40 ` Linus Torvalds
2025-02-20 22:09 ` Maciej W. Rozycki
2025-04-07 20:46 ` Maciej W. Rozycki
2025-04-08 0:34 ` Linus Torvalds
2025-04-08 8:37 ` Arnd Bergmann
2025-04-09 15:52 ` Eric W. Biederman
2025-04-09 20:59 ` Maciej W. Rozycki
2025-04-10 4:37 ` Eric W. Biederman
2025-02-20 14:25 ` Magnus Lindholm
2025-02-20 16:46 ` Matt Turner
2025-02-20 16:52 ` Matt Turner
2025-02-20 19:57 ` Maciej W. Rozycki
2025-02-20 17:54 ` Richard Henderson
2025-02-20 17:59 ` Linus Torvalds
2025-02-20 18:12 ` Richard Henderson [this message]
2025-02-20 19:07 ` Matt Turner
2025-02-20 20:09 ` Maciej W. Rozycki
2025-02-20 21:05 ` Maciej W. Rozycki
2025-02-25 20:44 ` Maciej W. Rozycki
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=dfb14748-c5b8-4a50-990b-d61765a6a75c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=arnd@arndb.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=ink@unseen.parts \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=mattst88@gmail.com \
--cc=paulmck@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®