From: Marc Zyngier <marc.zyngier@arm.com>
To: Christoffer Dall <christoffer.dall@arm.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Cc: kvm@vger.kernel.org, Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH v3 7/9] KVM: arm/arm64: vgic: Permit uaccess writes to return errors
Date: Mon, 16 Jul 2018 09:28:00 +0100 [thread overview]
Message-ID: <08e71965-e39e-430f-3db5-765283ba3a0f@arm.com> (raw)
In-Reply-To: <1531587940-2490-8-git-send-email-christoffer.dall@arm.com>
On 14/07/18 18:05, Christoffer Dall wrote:
> Currently we do not allow any vgic mmio write operations to fail, which
> makes sense from mmio traps from the guest. However, we should be able
> to report failures to userspace, if userspace writes incompatible values
> to read-only registers. Rework the internal interface to allow errors
> to be returned on the write side for userspace writes.
>
> Signed-off-by: Christoffer Dall <christoffer.dall@arm.com>
> ---
> virt/kvm/arm/vgic/vgic-mmio-v2.c | 26 +++++++++++++++++++++-----
> virt/kvm/arm/vgic/vgic-mmio-v3.c | 31 ++++++++++++++++++++++++-------
> virt/kvm/arm/vgic/vgic-mmio.c | 18 +++++++++++++-----
> virt/kvm/arm/vgic/vgic-mmio.h | 19 +++++++++++--------
> 4 files changed, 69 insertions(+), 25 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic/vgic-mmio-v2.c b/virt/kvm/arm/vgic/vgic-mmio-v2.c
> index 34e36fc..b79de42 100644
> --- a/virt/kvm/arm/vgic/vgic-mmio-v2.c
> +++ b/virt/kvm/arm/vgic/vgic-mmio-v2.c
> @@ -77,11 +77,26 @@ static void vgic_mmio_write_v2_misc(struct kvm_vcpu *vcpu,
> }
> }
>
> -static void vgic_mmio_uaccess_write_v2_group(struct kvm_vcpu *vcpu,
> - gpa_t addr, unsigned int len,
> - unsigned long val)
> +static int vgic_mmio_uaccess_write_v2_misc(struct kvm_vcpu *vcpu,
> + gpa_t addr, unsigned int len,
> + unsigned long val)
> +{
> + switch (addr & 0x0c) {
> + case GIC_DIST_IIDR:
> + if (val != vgic_mmio_read_v2_misc(vcpu, addr, len))
> + return -EINVAL;
> + }
> +
> + vgic_mmio_write_v2_misc(vcpu, addr, len, val);
> + return 0;
> +}
> +
> +static int vgic_mmio_uaccess_write_v2_group(struct kvm_vcpu *vcpu,
> + gpa_t addr, unsigned int len,
> + unsigned long val)
> {
> /* Ignore writes from userspace */
> + return 0;
> }
I think it'd make more sense if this patch came before the previous one
(change the prototype of the userspace accessor, and only then add a new
accessor that can return an error). It would avoid churn in the above
function, and you could move vgic_mmio_uaccess_write_v2_misc into patch 6.
Not a big deal though, as the code is otherwise perfectly fine.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-07-16 8:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 17:05 [PATCH v3 0/9] KVM: arm/arm64: vgic: Virtual interrupt grouping support Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 1/9] KVM: arm/arm64: vgic: Define GICD_IIDR fields for GICv2 and GIv3 Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 2/9] KVM: arm/arm64: vgic: Keep track of implementation revision Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 3/9] KVM: arm/arm64: vgic: GICv2 IGROUPR should read as zero Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 4/9] KVM: arm/arm64: vgic: Add group field to struct irq Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 5/9] KVM: arm/arm64: vgic: Signal IRQs using their configured group Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 6/9] KVM: arm/arm64: vgic: Allow configuration of interrupt groups Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 7/9] KVM: arm/arm64: vgic: Permit uaccess writes to return errors Christoffer Dall
2018-07-16 8:28 ` Marc Zyngier [this message]
2018-07-16 9:59 ` Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 8/9] KVM: arm/arm64: vgic: Let userspace opt-in to writable v2 IGROUPR Christoffer Dall
2018-07-16 8:38 ` Marc Zyngier
2018-07-16 9:46 ` Christoffer Dall
2018-07-16 11:39 ` Christoffer Dall
2018-07-14 17:05 ` [PATCH v3 9/9] KVM: arm/arm64: vgic: Update documentation of the GICv2 device Christoffer Dall
2018-07-16 8:52 ` Marc Zyngier
2018-07-16 9:54 ` Christoffer Dall
2018-07-16 10:34 ` Christoffer Dall
2018-07-16 11:07 ` Marc Zyngier
2018-07-16 11:38 ` Christoffer Dall
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=08e71965-e39e-430f-3db5-765283ba3a0f@arm.com \
--to=marc.zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--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