From: Ada Couprie Diaz <ada.coupriediaz@arm.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Barry Song <baohua@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Xu Kuohai <xukuohai@huaweicloud.com>,
Lucas Wei <lucaswei@google.com>,
Andre Przywara <andre.przywara@arm.com>,
Mark Brown <broonie@kernel.org>, Marc Zyngier <maz@kernel.org>,
Tejun Heo <tj@kernel.org>, Oliver Upton <oupton@kernel.org>,
Will Deacon <will@kernel.org>,
Sascha Bischoff <Sascha.Bischoff@arm.com>
Subject: Re: [PATCH 1/2] arm64: insn: clean-up memory barrier types
Date: Mon, 19 Oct 2026 16:26:29 +0100 [thread overview]
Message-ID: <4fcc7fd2-0314-49bf-8994-6ef570700c88@arm.com> (raw)
In-Reply-To: <d8c784c0-ee8b-451f-879d-c3890f8dc63c@arm.com>
Hi Vladimir,
On 19/10/2026 11:07, Vladimir Murzin wrote:
> Hi Ada,
>
> On 10/16/26 17:51, Ada Couprie Diaz wrote:
>> Replace magic-numbers for offset and mask with shared defines.
>>
>> Re-order the types enum by value, matching the Arm ARM, and
>> define them with their proper values, simplifying their use.
>>
>> Arm ARM DDI 0487 version M.c[0] deprecated a number of types
>> used as options for the DMB and DSB instructions, with no change
>> in behaviour.
>> The deprecated types are not used in the kernel, so remove them
>> from our instruction generation framework and add the missing
>> `AARCH64_INSN_MB_OSH` case in `__get_barrier_crm_val()`.
>>
> Nitpick: this is slightly confusing since __get_barrier_crm_val()
> gets converted into __is_valid_barrier_type()
Ah yes, as with patch 2 I did forget this when I reworked this part
of the changes, my mistake. Thanks !
>> This simplifies the switch-case and now covers all the enum types,
>> which allows for making the DSB and DMB generation non instrumentable
>> in a follow-up commit.
>>
>> [0]: https://support.arm.com/documentation/ddi0487/mc/
>> (See C6.2.150, C6.2.152)
>>
>> Signed-off-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
>> ---
>> arch/arm64/include/asm/insn.h | 22 ++++++++----------
>> arch/arm64/lib/insn.c | 44 ++++++++++++-----------------------
>> 2 files changed, 25 insertions(+), 41 deletions(-)
>> [...]
> FWIW,
>
> Reviewed-by: Vladimir Murzin <vladimir.murzin@arm.com>
Thanks for having a look !
Kind regards,
Ada
next prev parent reply other threads:[~2026-10-19 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 16:51 [PATCH 0/2] arm64: insn: clean-up memory barrier generation Ada Couprie Diaz
2026-10-16 16:51 ` [PATCH 1/2] arm64: insn: clean-up memory barrier types Ada Couprie Diaz
2026-10-19 10:07 ` Vladimir Murzin
2026-10-19 15:26 ` Ada Couprie Diaz [this message]
2026-10-16 16:51 ` [PATCH 2/2] arm64: insn: make `aarch64_insn_gen_d{m,s}b()` alternative-safe Ada Couprie Diaz
2026-10-19 10:49 ` Vladimir Murzin
2026-10-19 15:24 ` Ada Couprie Diaz
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=4fcc7fd2-0314-49bf-8994-6ef570700c88@arm.com \
--to=ada.coupriediaz@arm.com \
--cc=Sascha.Bischoff@arm.com \
--cc=andre.przywara@arm.com \
--cc=baohua@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=lucaswei@google.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=puranjay@kernel.org \
--cc=tj@kernel.org \
--cc=vladimir.murzin@arm.com \
--cc=will@kernel.org \
--cc=xukuohai@huaweicloud.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