From: Ayan Kumar Halder <ayan.kumar.halder@amd.com>
To: <xen-devel@lists.xenproject.org>
Cc: <sstabellini@kernel.org>, <stefanos@xilinx.com>, <julien@xen.org>,
<Volodymyr_Babchuk@epam.com>, <bertrand.marquis@arm.com>,
<michal.orzel@amd.com>, Ayan Kumar Halder <ayankuma@amd.com>,
"Ayan Kumar Halder" <ayan.kumar.halder@amd.com>
Subject: [XEN v2] xen/Arm: Enforce alignment check for atomic read/write
Date: Fri, 4 Nov 2022 16:23:55 +0000 [thread overview]
Message-ID: <20221104162355.23369-1-ayan.kumar.halder@amd.com> (raw)
From: Ayan Kumar Halder <ayankuma@amd.com>
Refer ARM DDI 0487I.a ID081822, B2.2.1
"Requirements for single-copy atomicity
- A read that is generated by a load instruction that loads a single
general-purpose register and is aligned to the size of the read in the
instruction is single-copy atomic.
-A write that is generated by a store instruction that stores a single
general-purpose register and is aligned to the size of the write in the
instruction is single-copy atomic"
On AArch32, the alignment check is enabled at boot time by setting HSCTLR.A bit.
("HSCTLR, Hyp System Control Register").
However in AArch64, alignment check is not enabled at boot time.
Thus, one needs to check for alignment when performing atomic operations.
Signed-off-by: Ayan Kumar Halder <ayan.kumar.halder@amd.com>
Reviewed-by: Michal Orzel <michal.orzel@amd.com
---
Changes from :-
v1 - 1. Referred to the latest Arm Architecture Reference Manual in the commit
message.
xen/arch/arm/include/asm/atomic.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/arch/arm/include/asm/atomic.h b/xen/arch/arm/include/asm/atomic.h
index 1f60c28b1b..64314d59b3 100644
--- a/xen/arch/arm/include/asm/atomic.h
+++ b/xen/arch/arm/include/asm/atomic.h
@@ -78,6 +78,7 @@ static always_inline void read_atomic_size(const volatile void *p,
void *res,
unsigned int size)
{
+ ASSERT(IS_ALIGNED((vaddr_t)p, size));
switch ( size )
{
case 1:
@@ -102,6 +103,7 @@ static always_inline void write_atomic_size(volatile void *p,
void *val,
unsigned int size)
{
+ ASSERT(IS_ALIGNED((vaddr_t)p, size));
switch ( size )
{
case 1:
--
2.17.1
next reply other threads:[~2022-11-04 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 16:23 Ayan Kumar Halder [this message]
2022-11-04 16:32 ` [XEN v2] xen/Arm: Enforce alignment check for atomic read/write Bertrand Marquis
2022-11-06 17:54 ` Julien Grall
2022-11-07 10:36 ` Ayan Kumar Halder
2022-11-07 10:44 ` Julien Grall
2022-11-07 12:49 ` Ayan Kumar Halder
2022-11-07 18:06 ` Julien Grall
2022-11-08 7:26 ` Michal Orzel
2022-11-08 8:34 ` Bertrand Marquis
2022-11-08 9:48 ` Ayan Kumar Halder
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=20221104162355.23369-1-ayan.kumar.halder@amd.com \
--to=ayan.kumar.halder@amd.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayankuma@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=stefanos@xilinx.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.