From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 10/11] KVM: arm/arm64: prepare GICv3 emulation to use kvm_io_bus MMIO handling
Date: Fri, 27 Mar 2015 07:34:50 +0000 [thread overview]
Message-ID: <20150327073450.5cc33e5c@arm.com> (raw)
In-Reply-To: <5514A0D4.4040302@arm.com>
On Fri, 27 Mar 2015 00:14:12 +0000
Andre Przywara <andre.przywara@arm.com> wrote:
> On 03/26/2015 10:06 PM, Marc Zyngier wrote:
> > On Thu, 26 Mar 2015 14:39:37 +0000
> > Andre Przywara <andre.przywara@arm.com> wrote:
> >
> >> Using the framework provided by the recent vgic.c changes, we
> >> register a kvm_io_bus device on mapping the virtual GICv3 resources.
> >> The distributor mapping is pretty straight forward, but the
> >> redistributors need some more love, since they need to be tagged with
> >> the respective redistributor (read: VCPU) they are connected with.
> >> We use the kvm_io_bus framework to register one devices per VCPU.
> >>
> >> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> >> ---
> >> include/kvm/arm_vgic.h | 1 +
> >> virt/kvm/arm/vgic-v3-emul.c | 39 ++++++++++++++++++++++++++++++++++++++-
> >> 2 files changed, 39 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/include/kvm/arm_vgic.h b/include/kvm/arm_vgic.h
> >> index 4523984..d6705f4 100644
> >> --- a/include/kvm/arm_vgic.h
> >> +++ b/include/kvm/arm_vgic.h
> >> @@ -252,6 +252,7 @@ struct vgic_dist {
> >>
> >> struct vgic_vm_ops vm_ops;
> >> struct vgic_io_device dist_iodev;
> >> + struct vgic_io_device *redist_iodevs;
> >> };
> >>
> >> struct vgic_v2_cpu_if {
> >> diff --git a/virt/kvm/arm/vgic-v3-emul.c b/virt/kvm/arm/vgic-v3-emul.c
> >> index 2f03a36..eb1a797 100644
> >> --- a/virt/kvm/arm/vgic-v3-emul.c
> >> +++ b/virt/kvm/arm/vgic-v3-emul.c
> >> @@ -758,6 +758,9 @@ static int vgic_v3_map_resources(struct kvm *kvm,
> >> {
> >> int ret = 0;
> >> struct vgic_dist *dist = &kvm->arch.vgic;
> >> + gpa_t rdbase = dist->vgic_redist_base;
> >> + struct vgic_io_device *iodevs = NULL;
> >> + int i;
> >>
> >> if (!irqchip_in_kernel(kvm))
> >> return 0;
> >> @@ -783,7 +786,41 @@ static int vgic_v3_map_resources(struct kvm *kvm,
> >> goto out;
> >> }
> >>
> >> - kvm->arch.vgic.ready = true;
> >> + ret = vgic_register_kvm_io_dev(kvm, dist->vgic_dist_base,
> >> + GIC_V3_DIST_SIZE, vgic_v3_dist_ranges,
> >> + -1, &dist->dist_iodev);
> >
> >> + if (ret)
> >> + goto out;
> >> +
> >> + iodevs = kcalloc(dist->nr_cpus, sizeof(iodevs[0]), GFP_KERNEL);
> >> + if (!iodevs) {
> >> + ret = -ENOMEM;
> >> + goto out_unregister;
> >> + }
> >> +
> >> + for (i = 0; i < dist->nr_cpus; i++) {
> >> + ret = vgic_register_kvm_io_dev(kvm, rdbase,
> >> + SZ_128K, vgic_redist_ranges,
> >> + i, &iodevs[i]);
> >
> > This looks really weird. You seems to be mapping all redistributors at
> > the same IPA. Have you actually tested this with an SMP guest?
>
> But the patch continues:
>
> + if (ret)
> + goto out_unregister;
> + rdbase += GIC_V3_REDIST_SIZE;
>
> Is that too confusing to re-use the rdbase variable? The spec speaks of
> RD_base for each redistributor, so that seemed sane to me.
> Shall I add a comment or use "rdbase + i * GIC_V3_REDIST_SIZE" for clarity?
That would have been nicer, but let's face the harsh truth: I can't
read, ignore me (well, for this time only ;-).
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2015-03-27 7:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 14:39 [PATCH v3 00/11] KVM: arm/arm64: move VGIC MMIO to kvm_io_bus Andre Przywara
2015-03-26 14:39 ` [PATCH v3 01/11] KVM: Redesign kvm_io_bus_ API to pass VCPU structure to the callbacks Andre Przywara
2015-03-26 14:39 ` [PATCH v3 02/11] KVM: move iodev.h from virt/kvm/ to include/kvm Andre Przywara
2015-03-26 14:39 ` [PATCH v3 03/11] KVM: arm/arm64: remove now unneeded include directory from Makefile Andre Przywara
2015-03-26 14:39 ` [PATCH v3 04/11] KVM: x86: " Andre Przywara
2015-03-26 14:39 ` [PATCH v3 05/11] KVM: arm/arm64: rename struct kvm_mmio_range to vgic_io_range Andre Przywara
2015-03-26 14:39 ` [PATCH v3 06/11] KVM: arm/arm64: simplify vgic_find_range() and callers Andre Przywara
2015-03-26 14:39 ` [PATCH v3 07/11] KVM: arm/arm64: implement kvm_io_bus MMIO handling for the VGIC Andre Przywara
2015-03-27 16:00 ` Christoffer Dall
2015-03-26 14:39 ` [PATCH v3 08/11] KVM: arm/arm64: prepare GICv2 emulation to be handled by kvm_io_bus Andre Przywara
2015-03-26 21:46 ` Marc Zyngier
2015-03-27 16:01 ` Christoffer Dall
2015-03-26 14:39 ` [PATCH v3 09/11] KVM: arm/arm64: merge GICv3 RD_base and SGI_base register frames Andre Przywara
2015-03-26 21:53 ` Marc Zyngier
2015-03-27 0:14 ` Andre Przywara
2015-03-27 16:01 ` Christoffer Dall
2015-03-26 14:39 ` [PATCH v3 10/11] KVM: arm/arm64: prepare GICv3 emulation to use kvm_io_bus MMIO handling Andre Przywara
2015-03-26 22:06 ` Marc Zyngier
2015-03-27 0:14 ` Andre Przywara
2015-03-27 7:34 ` Marc Zyngier [this message]
2015-03-27 16:01 ` Christoffer Dall
2015-03-26 14:39 ` [PATCH v3 11/11] KVM: arm/arm64: rework MMIO abort handling to use KVM MMIO bus Andre Przywara
2015-03-27 16:00 ` Christoffer Dall
2015-03-28 1:13 ` [PATCH v3a " Andre Przywara
2015-03-30 10:47 ` Marc Zyngier
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=20150327073450.5cc33e5c@arm.com \
--to=marc.zyngier@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).