From: Kristina Martsenko <kristina.martsenko@arm.com> To: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev Cc: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>, Oliver Upton <oliver.upton@linux.dev>, James Morse <james.morse@arm.com>, Suzuki K Poulose <suzuki.poulose@arm.com>, Zenghui Yu <yuzenghui@huawei.com>, Mark Rutland <mark.rutland@arm.com>, Mark Brown <broonie@kernel.org>, Luis Machado <luis.machado@arm.com>, Vladimir Murzin <vladimir.murzin@arm.com>, linux-kernel@vger.kernel.org Subject: [PATCH 00/10] arm64: support Armv8.8 memcpy instructions in userspace Date: Thu, 16 Feb 2023 16:00:02 +0000 [thread overview] Message-ID: <20230216160012.272345-1-kristina.martsenko@arm.com> (raw) The Armv8.8 extension adds new instructions to perform memcpy(), memset() and memmove() operations in hardware (FEAT_MOPS). The aim is to avoid having many different performance-optimal memcpy implementations in software (tailored to CPU model and copy size) and the overhead of selecting between them. The new instructions are intended to be at least as fast as any alternative instruction sequence. This series adds support for using the new instructions in userspace. The most noteworthy part is some exception handling for when there are different memcpy implementations in the same system. In addition, the first patches in the series set up basic handling for the new HCRX_EL2 register (added in Armv8.7), which is needed to disable MOPS in KVM guests for now. Support for using memcpy instructions in KVM guests will follow in a future series, as well as kselftests and more debug support. Kristina Martsenko (10): KVM: arm64: initialize HCRX_EL2 arm64: cpufeature: detect FEAT_HCX KVM: arm64: switch HCRX_EL2 between host and guest arm64: mops: document boot requirements for MOPS arm64: mops: don't disable host MOPS instructions from EL2 KVM: arm64: hide MOPS from guests arm64: mops: handle MOPS exceptions arm64: mops: handle single stepping after MOPS exception arm64: mops: detect and enable FEAT_MOPS arm64: mops: allow disabling MOPS from the kernel command line .../admin-guide/kernel-parameters.txt | 3 ++ Documentation/arm64/booting.rst | 8 +++ Documentation/arm64/cpu-feature-registers.rst | 2 + Documentation/arm64/elf_hwcaps.rst | 3 ++ arch/arm64/include/asm/el2_setup.h | 8 --- arch/arm64/include/asm/esr.h | 11 +++- arch/arm64/include/asm/exception.h | 1 + arch/arm64/include/asm/hwcap.h | 1 + arch/arm64/include/asm/kvm_arm.h | 4 ++ arch/arm64/include/uapi/asm/hwcap.h | 1 + arch/arm64/kernel/cpufeature.c | 31 +++++++++++ arch/arm64/kernel/cpuinfo.c | 1 + arch/arm64/kernel/entry-common.c | 11 ++++ arch/arm64/kernel/head.S | 7 +++ arch/arm64/kernel/idreg-override.c | 2 + arch/arm64/kernel/traps.c | 51 +++++++++++++++++++ arch/arm64/kvm/hyp/include/hyp/switch.h | 6 +++ arch/arm64/kvm/hyp/nvhe/hyp-init.S | 6 +++ arch/arm64/kvm/sys_regs.c | 1 + arch/arm64/tools/cpucaps | 2 + 20 files changed, 151 insertions(+), 9 deletions(-) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Kristina Martsenko <kristina.martsenko@arm.com> To: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev Cc: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>, Oliver Upton <oliver.upton@linux.dev>, James Morse <james.morse@arm.com>, Suzuki K Poulose <suzuki.poulose@arm.com>, Zenghui Yu <yuzenghui@huawei.com>, Mark Rutland <mark.rutland@arm.com>, Mark Brown <broonie@kernel.org>, Luis Machado <luis.machado@arm.com>, Vladimir Murzin <vladimir.murzin@arm.com>, linux-kernel@vger.kernel.org Subject: [PATCH 00/10] arm64: support Armv8.8 memcpy instructions in userspace Date: Thu, 16 Feb 2023 16:00:02 +0000 [thread overview] Message-ID: <20230216160012.272345-1-kristina.martsenko@arm.com> (raw) The Armv8.8 extension adds new instructions to perform memcpy(), memset() and memmove() operations in hardware (FEAT_MOPS). The aim is to avoid having many different performance-optimal memcpy implementations in software (tailored to CPU model and copy size) and the overhead of selecting between them. The new instructions are intended to be at least as fast as any alternative instruction sequence. This series adds support for using the new instructions in userspace. The most noteworthy part is some exception handling for when there are different memcpy implementations in the same system. In addition, the first patches in the series set up basic handling for the new HCRX_EL2 register (added in Armv8.7), which is needed to disable MOPS in KVM guests for now. Support for using memcpy instructions in KVM guests will follow in a future series, as well as kselftests and more debug support. Kristina Martsenko (10): KVM: arm64: initialize HCRX_EL2 arm64: cpufeature: detect FEAT_HCX KVM: arm64: switch HCRX_EL2 between host and guest arm64: mops: document boot requirements for MOPS arm64: mops: don't disable host MOPS instructions from EL2 KVM: arm64: hide MOPS from guests arm64: mops: handle MOPS exceptions arm64: mops: handle single stepping after MOPS exception arm64: mops: detect and enable FEAT_MOPS arm64: mops: allow disabling MOPS from the kernel command line .../admin-guide/kernel-parameters.txt | 3 ++ Documentation/arm64/booting.rst | 8 +++ Documentation/arm64/cpu-feature-registers.rst | 2 + Documentation/arm64/elf_hwcaps.rst | 3 ++ arch/arm64/include/asm/el2_setup.h | 8 --- arch/arm64/include/asm/esr.h | 11 +++- arch/arm64/include/asm/exception.h | 1 + arch/arm64/include/asm/hwcap.h | 1 + arch/arm64/include/asm/kvm_arm.h | 4 ++ arch/arm64/include/uapi/asm/hwcap.h | 1 + arch/arm64/kernel/cpufeature.c | 31 +++++++++++ arch/arm64/kernel/cpuinfo.c | 1 + arch/arm64/kernel/entry-common.c | 11 ++++ arch/arm64/kernel/head.S | 7 +++ arch/arm64/kernel/idreg-override.c | 2 + arch/arm64/kernel/traps.c | 51 +++++++++++++++++++ arch/arm64/kvm/hyp/include/hyp/switch.h | 6 +++ arch/arm64/kvm/hyp/nvhe/hyp-init.S | 6 +++ arch/arm64/kvm/sys_regs.c | 1 + arch/arm64/tools/cpucaps | 2 + 20 files changed, 151 insertions(+), 9 deletions(-) -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-02-16 16:01 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-16 16:00 Kristina Martsenko [this message] 2023-02-16 16:00 ` [PATCH 00/10] arm64: support Armv8.8 memcpy instructions in userspace Kristina Martsenko 2023-02-16 16:00 ` [PATCH 01/10] KVM: arm64: initialize HCRX_EL2 Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 14:25 ` Catalin Marinas 2023-03-17 14:25 ` Catalin Marinas 2023-02-16 16:00 ` [PATCH 02/10] arm64: cpufeature: detect FEAT_HCX Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 14:25 ` Catalin Marinas 2023-03-17 14:25 ` Catalin Marinas 2023-02-16 16:00 ` [PATCH 03/10] KVM: arm64: switch HCRX_EL2 between host and guest Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-02-16 16:20 ` Mark Brown 2023-02-16 16:20 ` Mark Brown 2023-02-22 18:36 ` Kristina Martsenko 2023-02-22 18:36 ` Kristina Martsenko 2023-02-16 16:35 ` Marc Zyngier 2023-02-16 16:35 ` Marc Zyngier 2023-02-22 18:42 ` Kristina Martsenko 2023-02-22 18:42 ` Kristina Martsenko 2023-02-16 16:00 ` [PATCH 04/10] arm64: mops: document boot requirements for MOPS Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 15:07 ` Catalin Marinas 2023-03-17 15:07 ` Catalin Marinas 2023-03-24 1:00 ` Kristina Martsenko 2023-03-24 1:00 ` Kristina Martsenko 2023-04-04 10:50 ` Catalin Marinas 2023-04-04 10:50 ` Catalin Marinas 2023-04-11 16:57 ` Kristina Martsenko 2023-04-11 16:57 ` Kristina Martsenko 2023-02-16 16:00 ` [PATCH 05/10] arm64: mops: don't disable host MOPS instructions from EL2 Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 15:07 ` Catalin Marinas 2023-03-17 15:07 ` Catalin Marinas 2023-02-16 16:00 ` [PATCH 06/10] KVM: arm64: hide MOPS from guests Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 15:09 ` Catalin Marinas 2023-03-17 15:09 ` Catalin Marinas 2023-02-16 16:00 ` [PATCH 07/10] arm64: mops: handle MOPS exceptions Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 15:45 ` Catalin Marinas 2023-03-17 15:45 ` Catalin Marinas 2023-02-16 16:00 ` [PATCH 08/10] arm64: mops: handle single stepping after MOPS exception Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 16:02 ` Catalin Marinas 2023-03-17 16:02 ` Catalin Marinas 2023-02-16 16:00 ` [PATCH 09/10] arm64: mops: detect and enable FEAT_MOPS Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-02-16 16:22 ` Mark Brown 2023-02-16 16:22 ` Mark Brown 2023-03-17 16:03 ` Catalin Marinas 2023-03-17 16:03 ` Catalin Marinas 2023-02-16 16:00 ` [PATCH 10/10] arm64: mops: allow disabling MOPS from the kernel command line Kristina Martsenko 2023-02-16 16:00 ` Kristina Martsenko 2023-03-17 16:04 ` Catalin Marinas 2023-03-17 16:04 ` Catalin Marinas
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=20230216160012.272345-1-kristina.martsenko@arm.com \ --to=kristina.martsenko@arm.com \ --cc=broonie@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=james.morse@arm.com \ --cc=kvmarm@lists.linux.dev \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=luis.machado@arm.com \ --cc=mark.rutland@arm.com \ --cc=maz@kernel.org \ --cc=oliver.upton@linux.dev \ --cc=suzuki.poulose@arm.com \ --cc=vladimir.murzin@arm.com \ --cc=will@kernel.org \ --cc=yuzenghui@huawei.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: linkBe 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.