From: Dave Martin <Dave.Martin@arm.com>
To: Andrew Jones <drjones@redhat.com>
Cc: maz@kernel.org, xu910121@sina.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v2 2/3] KVM: arm64: Check RAZ visibility in ID register accessors
Date: Tue, 3 Nov 2020 11:23:54 +0000 [thread overview]
Message-ID: <20201103112354.GH6882@arm.com> (raw)
In-Reply-To: <20201102185037.49248-3-drjones@redhat.com>
On Mon, Nov 02, 2020 at 07:50:36PM +0100, Andrew Jones wrote:
> The instruction encodings of ID registers are preallocated. Until an
> encoding is assigned a purpose the register is RAZ. KVM's general ID
> register accessor functions already support both paths, RAZ or not.
> If for each ID register we can determine if it's RAZ or not, then all
> ID registers can build on the general functions. The register visibility
> function allows us to check whether a register should be completely
> hidden or not, extending it to also report when the register should
> be RAZ or not allows us to use it for ID registers as well.
Nit: no statement of what the patch does.
You might want to point out that the introduced REG_RAZ functionality is
intentionally not used in this patch.
> No functional change intended.
>
> Signed-off-by: Andrew Jones <drjones@redhat.com>
> ---
> arch/arm64/kvm/sys_regs.c | 19 ++++++++++++++++---
> arch/arm64/kvm/sys_regs.h | 10 ++++++++++
> 2 files changed, 26 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
> index 6ff0c15531ca..b8822a20b1ea 100644
> --- a/arch/arm64/kvm/sys_regs.c
> +++ b/arch/arm64/kvm/sys_regs.c
> @@ -1153,6 +1153,12 @@ static u64 read_id_reg(const struct kvm_vcpu *vcpu,
> return val;
> }
>
> +static unsigned int id_visibility(const struct kvm_vcpu *vcpu,
> + const struct sys_reg_desc *r)
> +{
> + return 0;
> +}
> +
> /* cpufeature ID register access trap handlers */
>
> static bool __access_id_reg(struct kvm_vcpu *vcpu,
> @@ -1171,7 +1177,9 @@ static bool access_id_reg(struct kvm_vcpu *vcpu,
> struct sys_reg_params *p,
> const struct sys_reg_desc *r)
> {
> - return __access_id_reg(vcpu, p, r, false);
> + bool raz = sysreg_visible_as_raz(vcpu, r);
> +
> + return __access_id_reg(vcpu, p, r, raz);
> }
>
> static bool access_raz_id_reg(struct kvm_vcpu *vcpu,
> @@ -1283,13 +1291,17 @@ static int __set_id_reg(const struct kvm_vcpu *vcpu,
> static int get_id_reg(struct kvm_vcpu *vcpu, const struct sys_reg_desc *rd,
> const struct kvm_one_reg *reg, void __user *uaddr)
> {
> - return __get_id_reg(vcpu, rd, uaddr, false);
> + bool raz = sysreg_visible_as_raz(vcpu, rd);
> +
> + return __get_id_reg(vcpu, rd, uaddr, raz);
> }
>
> static int set_id_reg(struct kvm_vcpu *vcpu, const struct sys_reg_desc *rd,
> const struct kvm_one_reg *reg, void __user *uaddr)
> {
> - return __set_id_reg(vcpu, rd, uaddr, false);
> + bool raz = sysreg_visible_as_raz(vcpu, rd);
> +
> + return __set_id_reg(vcpu, rd, uaddr, raz);
> }
>
> static int get_raz_id_reg(struct kvm_vcpu *vcpu, const struct sys_reg_desc *rd,
> @@ -1381,6 +1393,7 @@ static bool access_mte_regs(struct kvm_vcpu *vcpu, struct sys_reg_params *p,
> .access = access_id_reg, \
> .get_user = get_id_reg, \
> .set_user = set_id_reg, \
> + .visibility = id_visibility, \
This is just the default for ID_SANITISED, right?
> }
>
> /*
> diff --git a/arch/arm64/kvm/sys_regs.h b/arch/arm64/kvm/sys_regs.h
> index 5a6fc30f5989..9d3ef7cfa116 100644
> --- a/arch/arm64/kvm/sys_regs.h
> +++ b/arch/arm64/kvm/sys_regs.h
> @@ -61,6 +61,7 @@ struct sys_reg_desc {
>
> #define REG_HIDDEN_USER (1 << 0) /* hidden from userspace ioctls */
> #define REG_HIDDEN_GUEST (1 << 1) /* hidden from guest */
> +#define REG_RAZ (1 << 2) /* RAZ from userspace ioctls and guest */
>
> static __printf(2, 3)
> inline void print_sys_reg_msg(const struct sys_reg_params *p,
> @@ -129,6 +130,15 @@ static inline bool sysreg_hidden_from_user(const struct kvm_vcpu *vcpu,
> return r->visibility(vcpu, r) & REG_HIDDEN_USER;
> }
>
> +static inline bool sysreg_visible_as_raz(const struct kvm_vcpu *vcpu,
> + const struct sys_reg_desc *r)
> +{
> + if (likely(!r->visibility))
> + return false;
> +
> + return r->visibility(vcpu, r) & REG_RAZ;
> +}
> +
[...]
Looks reasonable, I think.
Cheers
---Dave
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-11-03 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 18:50 [PATCH v2 0/3] KVM: arm64: Fix get-reg-list regression Andrew Jones
2020-11-02 18:50 ` [PATCH v2 1/3] KVM: arm64: Don't hide ID registers from userspace Andrew Jones
2020-11-03 11:18 ` Dave Martin
2020-11-03 13:32 ` Andrew Jones
2020-11-04 16:11 ` Dave Martin
2020-11-02 18:50 ` [PATCH v2 2/3] KVM: arm64: Check RAZ visibility in ID register accessors Andrew Jones
2020-11-03 11:23 ` Dave Martin [this message]
2020-11-03 13:38 ` Andrew Jones
2020-11-04 16:31 ` Dave Martin
2020-11-02 18:50 ` [PATCH v2 3/3] KVM: arm64: Remove AA64ZFR0_EL1 accessors Andrew Jones
2020-11-03 11:32 ` Dave Martin
2020-11-03 13:46 ` Andrew Jones
2020-11-04 16:36 ` Dave Martin
2020-11-03 11:37 ` [PATCH v2 0/3] KVM: arm64: Fix get-reg-list regression Dave Martin
2020-11-03 13:52 ` Andrew Jones
2020-11-04 16:41 ` Dave Martin
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=20201103112354.GH6882@arm.com \
--to=dave.martin@arm.com \
--cc=drjones@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=xu910121@sina.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