From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 03/19] arm64: introduce sysreg_clear_set()
Date: Fri, 1 Jun 2018 12:24:25 +0100 [thread overview]
Message-ID: <20180601112441.37810-4-mark.rutland@arm.com> (raw)
In-Reply-To: <20180601112441.37810-1-mark.rutland@arm.com>
Currently we have a couple of helpers to manipulate bits in particular
sysregs:
* config_sctlr_el1(u32 clear, u32 set)
* change_cpacr(u64 val, u64 mask)
The parameters of these differ in naming convention, order, and size,
which is unfortunate. They also differ slightly in behaviour, as
change_cpacr() skips the sysreg write if the bits are unchanged, which
is a useful optimization when sysreg writes are expensive.
Before we gain more yet another sysreg manipulation function, let's
unify these with a common helper, providing a consistent order for
clear/set operands, and the write skipping behaviour from
change_cpacr(). Code will be migrated to the new helper in subsequent
patches.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Dave Martin <dave.martin@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>
---
arch/arm64/include/asm/sysreg.h | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/include/asm/sysreg.h b/arch/arm64/include/asm/sysreg.h
index bd1d1194a5e7..b52762769329 100644
--- a/arch/arm64/include/asm/sysreg.h
+++ b/arch/arm64/include/asm/sysreg.h
@@ -729,6 +729,17 @@ asm(
asm volatile("msr_s " __stringify(r) ", %x0" : : "rZ" (__val)); \
} while (0)
+/*
+ * Modify bits in a sysreg. Bits in the clear mask are zeroed, then bits in the
+ * set mask are set. Other bits are left as-is.
+ */
+#define sysreg_clear_set(sysreg, clear, set) do { \
+ u64 __scs_val = read_sysreg(sysreg); \
+ u64 __scs_new = (__scs_val & ~(u64)(clear)) | (set); \
+ if (__scs_new != __scs_val) \
+ write_sysreg(__scs_new, sysreg); \
+} while (0)
+
static inline void config_sctlr_el1(u32 clear, u32 set)
{
u32 val;
--
2.11.0
next prev parent reply other threads:[~2018-06-01 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 11:24 [PATCHv2 00/19] arm64: invoke syscalls with pt_regs Mark Rutland
2018-06-01 11:24 ` [PATCHv2 01/19] arm64: consistently use unsigned long for thread flags Mark Rutland
2018-06-01 11:24 ` [PATCHv2 02/19] arm64: move SCTLR_EL{1, 2} assertions to <asm/sysreg.h> Mark Rutland
2018-06-14 16:44 ` [PATCHv2 02/19] arm64: move SCTLR_EL{1,2} " Will Deacon
2018-06-01 11:24 ` Mark Rutland [this message]
2018-06-01 11:24 ` [PATCHv2 04/19] arm64: kill config_sctlr_el1() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 05/19] arm64: kill change_cpacr() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 06/19] arm64: move sve_user_{enable, disable} to <asm/fpsimd.h> Mark Rutland
2018-06-01 11:24 ` [PATCHv2 07/19] arm64: remove sigreturn wrappers Mark Rutland
2018-06-01 11:24 ` [PATCHv2 08/19] arm64: convert raw syscall invocation to C Mark Rutland
2018-06-01 11:24 ` [PATCHv2 09/19] arm64: convert syscall trace logic " Mark Rutland
2018-06-01 11:24 ` [PATCHv2 10/19] arm64: convert native/compat syscall entry " Mark Rutland
2018-06-01 11:24 ` [PATCHv2 11/19] arm64: don't reload GPRs after apply_ssbd Mark Rutland
2018-06-01 14:41 ` Marc Zyngier
2018-06-01 11:24 ` [PATCHv2 12/19] arm64: zero GPRs upon entry from EL0 Mark Rutland
2018-06-01 11:24 ` [PATCHv2 13/19] kernel: add ksys_personality() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 14/19] kernel: add kcompat_sys_{f,}statfs64() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 15/19] arm64: remove in-kernel call to sys_personality() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 16/19] arm64: use {COMPAT,}SYSCALL_DEFINE0 for sigreturn Mark Rutland
2018-06-01 11:24 ` [PATCHv2 17/19] arm64: use SYSCALL_DEFINE6() for mmap Mark Rutland
2018-06-01 11:24 ` [PATCHv2 18/19] arm64: convert compat wrappers to C Mark Rutland
2018-06-01 11:24 ` [PATCHv2 19/19] arm64: implement syscall wrappers Mark Rutland
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=20180601112441.37810-4-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).