From: Michal Orzel <michal.orzel@arm.com> To: xen-devel@lists.xenproject.org Cc: Stefano Stabellini <sstabellini@kernel.org>, Julien Grall <julien@xen.org>, Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>, bertrand.marquis@arm.com, Julien Grall <jgrall@amazon.com> Subject: [PATCH v2 08/10] arm/page: Get rid of READ/WRITE_SYSREG32 Date: Tue, 27 Apr 2021 11:35:44 +0200 [thread overview] Message-ID: <20210427093546.30703-9-michal.orzel@arm.com> (raw) In-Reply-To: <20210427093546.30703-1-michal.orzel@arm.com> AArch64 registers are 64bit whereas AArch32 registers are 32bit or 64bit. MSR/MRS are expecting 64bit values thus we should get rid of helpers READ/WRITE_SYSREG32 in favour of using READ/WRITE_SYSREG. We should also use register_t type when reading sysregs which can correspond to uint64_t or uint32_t. Even though many AArch64 registers have upper 32bit reserved it does not mean that they can't be widen in the future. Modify accesses to CTR_EL0 to use READ/WRITE_SYSREG. Signed-off-by: Michal Orzel <michal.orzel@arm.com> Reviewed-by: Julien Grall <jgrall@amazon.com> --- xen/include/asm-arm/page.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xen/include/asm-arm/page.h b/xen/include/asm-arm/page.h index 131507a517..c6f9fb0d4e 100644 --- a/xen/include/asm-arm/page.h +++ b/xen/include/asm-arm/page.h @@ -137,10 +137,10 @@ extern size_t dcache_line_bytes; static inline size_t read_dcache_line_bytes(void) { - uint32_t ctr; + register_t ctr; /* Read CTR */ - ctr = READ_SYSREG32(CTR_EL0); + ctr = READ_SYSREG(CTR_EL0); /* Bits 16-19 are the log2 number of words in the cacheline. */ return (size_t) (4 << ((ctr >> 16) & 0xf)); -- 2.29.0
next prev parent reply other threads:[~2021-04-27 9:36 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-27 9:35 [PATCH v2 00/10] " Michal Orzel 2021-04-27 9:35 ` [PATCH v2 01/10] arm64/vfp: " Michal Orzel 2021-04-27 9:35 ` [PATCH v2 02/10] arm/domain: " Michal Orzel 2021-04-27 9:45 ` Julien Grall 2021-04-29 6:58 ` Michal Orzel 2021-04-27 9:35 ` [PATCH v2 03/10] arm: Modify type of actlr to register_t Michal Orzel 2021-04-27 9:47 ` Julien Grall 2021-04-29 7:10 ` Michal Orzel 2021-04-27 9:35 ` [PATCH v2 04/10] arm/gic: Remove member hcr of structure gic_v3 Michal Orzel 2021-04-27 9:48 ` Julien Grall 2021-04-27 9:35 ` [PATCH v2 05/10] arm/gic: Get rid of READ/WRITE_SYSREG32 Michal Orzel 2021-04-27 10:02 ` Julien Grall 2021-04-29 7:14 ` Michal Orzel 2021-04-27 9:35 ` [PATCH v2 06/10] arm/p2m: " Michal Orzel 2021-04-27 9:35 ` [PATCH v2 07/10] arm/mm: " Michal Orzel 2021-04-27 9:59 ` Julien Grall 2021-04-29 7:16 ` Michal Orzel 2021-04-27 9:35 ` Michal Orzel [this message] 2021-04-27 9:35 ` [PATCH v2 09/10] arm/time,vtimer: " Michal Orzel 2021-04-27 10:09 ` Julien Grall 2021-04-27 9:35 ` [PATCH v2 10/10] arm64: Change type of hsr, cpsr, spsr_el1 to uint64_t Michal Orzel 2021-04-27 11:09 ` Julien Grall 2021-04-29 8:53 ` Michal Orzel 2021-04-29 10:31 ` Tamas K Lengyel 2021-04-29 10:35 ` Julien Grall
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=20210427093546.30703-9-michal.orzel@arm.com \ --to=michal.orzel@arm.com \ --cc=Volodymyr_Babchuk@epam.com \ --cc=bertrand.marquis@arm.com \ --cc=jgrall@amazon.com \ --cc=julien@xen.org \ --cc=sstabellini@kernel.org \ --cc=xen-devel@lists.xenproject.org \ --subject='Re: [PATCH v2 08/10] arm/page: Get rid of READ/WRITE_SYSREG32' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).