From: Will Deacon <will@kernel.org>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Billy Laws <blaws05@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>,
Ryan Houdek <sonicadvance1@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-dev@igalia.com
Subject: Re: [RFC PATCH v3 1/1] arch: arm64: Implement unaligned atomic emulation
Date: Wed, 30 Sep 2026 14:29:46 +0100 [thread overview]
Message-ID: <ar0OyoPqGfmrkdH5@willie-the-truck> (raw)
In-Reply-To: <00227dc1-e01c-4de8-b3e3-3cd8de74cba9@igalia.com>
On Wed, Sep 30, 2026 at 07:29:22AM -0300, André Almeida wrote:
> Em 30/09/2026 04:48, Will Deacon escreveu:
> > On Tue, Sep 29, 2026 at 11:01:38PM -0300, André Almeida wrote:
> > > Implement support for emulating unaligned atomic operations on arm64.
> > > User applications that wish to enable support for this should use the
> > > pctrl() flag `PR_ARM64_UNALIGN_ATOMIC_EMULATE`.
> > >
> > > Signed-off-by: André Almeida <andrealmeid@igalia.com>
> > > ---
> > > arch/arm64/Kconfig | 6 +
> > > arch/arm64/include/asm/exception.h | 1 +
> > > arch/arm64/include/asm/processor.h | 5 +
> > > arch/arm64/include/asm/rwonce.h | 14 +-
> > > arch/arm64/include/asm/thread_info.h | 1 +
> > > arch/arm64/kernel/Makefile | 3 +-
> > > arch/arm64/kernel/process.c | 15 +
> > > arch/arm64/kernel/unaligned_atomic.c | 521 +++++++++++++++++++++++++++
> > > arch/arm64/mm/fault.c | 10 +
> > > include/uapi/linux/prctl.h | 5 +
> > > kernel/sys.c | 7 +-
> > > 11 files changed, 579 insertions(+), 9 deletions(-)
> > > create mode 100644 arch/arm64/kernel/unaligned_atomic.c
> >
> > No.
> >
> > I already explained to you why this doesn't work:
> >
> > https://lore.kernel.org/r/aV1YnOetDHhKe4hz@willie-the-truck
>
> Indeed, last time you raised some points, and then Ryan replied them. Is
> there any specific point that doesn't work? I couldn't find a reply for
> Ryan's answers:
>
> https://lore.kernel.org/all/CABnRqDf5EQUoXu=pJ6mj4-JfwAzEfcAE2cYrNzJANFycx7cMUA@mail.gmail.com/
So rather than get involved in the discussion, you did nothing for almost
a year and then resent the exact same patch? Why?
I don't think the implementation is correct and I don't think we should
be emulating this either. I hope I made that clear last year. Ryan
thinks it's "fine" due to the locking, but I don't see how that helps
with the example I gave.
You are apparently the author of this code, so you need to get involved
in the discussion if you want to move the needle.
Will
next prev parent reply other threads:[~2026-09-30 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 2:01 [RFC PATCH v3 0/1] arch: arm64: Implement unaligned atomic emulation André Almeida
2026-09-30 2:01 ` [RFC PATCH v3 1/1] " André Almeida
2026-09-30 7:48 ` Will Deacon
2026-09-30 10:29 ` André Almeida
2026-09-30 13:29 ` Will Deacon [this message]
2026-10-01 17:54 ` André Almeida
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=ar0OyoPqGfmrkdH5@willie-the-truck \
--to=will@kernel.org \
--cc=andrealmeid@igalia.com \
--cc=blaws05@gmail.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-dev@igalia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sonicadvance1@gmail.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