From: Catalin Marinas <catalin.marinas@arm.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
broonie@kernel.org, james.morse@arm.com, mark.rutland@arm.com,
maz@kernel.org, oliver.upton@linux.dev, shuah@kernel.org,
suzuki.poulose@arm.com, will@kernel.org, yuzenghui@huawei.com
Subject: Re: [PATCH v3 09/20] KVM: arm64: Save/restore PIE registers
Date: Fri, 2 Jun 2023 15:57:20 +0100 [thread overview]
Message-ID: <ZHoDUGLiEXRjQt/O@arm.com> (raw)
In-Reply-To: <20230511110337.3385517-10-joey.gouly@arm.com>
On Thu, May 11, 2023 at 12:03:26PM +0100, Joey Gouly wrote:
> Define the new system registers that PIE introduces and context switch them.
> The PIE feature is still hidden from the ID register, and not exposed to a VM.
>
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: James Morse <james.morse@arm.com>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: Zenghui Yu <yuzenghui@huawei.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
> arch/arm64/include/asm/kvm_host.h | 4 ++++
> arch/arm64/kvm/hyp/include/hyp/sysreg-sr.h | 8 ++++++++
> arch/arm64/kvm/sys_regs.c | 2 ++
> 3 files changed, 14 insertions(+)
>
> diff --git a/arch/arm64/include/asm/kvm_host.h b/arch/arm64/include/asm/kvm_host.h
> index f2cfb9ef1eeb..d9f079fbdaf4 100644
> --- a/arch/arm64/include/asm/kvm_host.h
> +++ b/arch/arm64/include/asm/kvm_host.h
> @@ -340,6 +340,10 @@ enum vcpu_sysreg {
> TFSR_EL1, /* Tag Fault Status Register (EL1) */
> TFSRE0_EL1, /* Tag Fault Status Register (EL0) */
>
> + /* Permission Indirection Extension registers */
> + PIR_EL1, /* Permission Indirection Register 1 (EL1) */
> + PIRE0_EL1, /* Permission Indirection Register 0 (EL1) */
These have been moved outside of the *_EL2 range as Marc asked. It looks
fine to me, waiting for an Ack from Marc/Oliver.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-02 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230511110337.3385517-1-joey.gouly@arm.com>
[not found] ` <20230511110337.3385517-12-joey.gouly@arm.com>
2023-05-26 9:33 ` [PATCH v3 11/20] arm64: add PTE_UXN/PTE_WRITE to SWAPPER_*_FLAGS Catalin Marinas
2023-06-01 12:02 ` [PATCH v3 00/20] Permission Indirection Extension Mark Brown
[not found] ` <20230511110337.3385517-9-joey.gouly@arm.com>
2023-06-02 14:56 ` [PATCH v3 08/20] KVM: arm64: Save/restore TCR2_EL1 Catalin Marinas
2023-06-03 8:34 ` Marc Zyngier
[not found] ` <20230511110337.3385517-10-joey.gouly@arm.com>
2023-06-02 14:57 ` Catalin Marinas [this message]
2023-06-03 8:35 ` [PATCH v3 09/20] KVM: arm64: Save/restore PIE registers Marc Zyngier
[not found] ` <20230511110337.3385517-11-joey.gouly@arm.com>
2023-06-03 8:35 ` [PATCH v3 10/20] KVM: arm64: expose ID_AA64MMFR3_EL1 to guests Marc Zyngier
2023-06-05 17:58 ` [PATCH v3 00/20] Permission Indirection Extension 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=ZHoDUGLiEXRjQt/O@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=nd@arm.com \
--cc=oliver.upton@linux.dev \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@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: 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).