mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Almeida" <andrealmeid@igalia.com>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	kernel-dev@igalia.com, Mark Brown <broonie@kernel.org>,
	Will Deacon <will@kernel.org>,
	Ryan Houdek <sonicadvance1@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Billy Laws <blaws05@gmail.com>
Subject: Re: [RFC PATCH v3 1/1] arch: arm64: Implement unaligned atomic emulation
Date: Wed, 14 Oct 2026 18:44:11 -0300	[thread overview]
Message-ID: <430b10e9-7c8a-44ad-904b-e579250b314a@igalia.com> (raw)
In-Reply-To: <20260930020138.2377090-2-andrealmeid@igalia.com>

Em 29/09/2026 23:01, André Almeida escreveu:
> 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`.
> 
As discussed at LPC 2026[1], the split lock emulation is probably the 
first thing that we want to figure from the atomics issues, given that 
is the trickiest one to emulate correctly given the need serialize two 
atomic instructions. As suggested by Mark, first we are going to work on 
an userspace solution that delivers correctness and from there we can 
better understand what the kernel could provide to help with performance 
improvements.

Thanks!
	André

[1] https://lpc.events/event/20/contributions/2594/

      parent reply	other threads:[~2026-10-14 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  2:01 [RFC PATCH v3 0/1] " 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
2026-10-01 17:54         ` André Almeida
2026-10-14 21:44   ` André Almeida [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=430b10e9-7c8a-44ad-904b-e579250b314a@igalia.com \
    --to=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 \
    --cc=will@kernel.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
all inboxes | Powered by JetHome®