From: Will Deacon <will.deacon@arm.com>
To: Joel Schopp <joel.schopp@amd.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"gleb@kernel.org" <gleb@kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
kvm-devel <kvm@vger.kernel.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Don Dutile <ddutile@redhat.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform
Date: Fri, 25 Jul 2014 15:08:51 +0100 [thread overview]
Message-ID: <20140725140851.GJ5269@arm.com> (raw)
In-Reply-To: <53D26392.9080602@amd.com>
Hi Joel,
On Fri, Jul 25, 2014 at 03:02:58PM +0100, Joel Schopp wrote:
> >>>> I can't think of any way of determining whether a particular
> >>>> system gets this right or wrong automatically, which suggests
> >>>> perhaps we need to allow the device tree to specify that the
> >>>> GICV is 64k-page-safe...
> >>> When we support such systems, I also think we'll need a device-tree change.
> >>> My main concern right now is stopping the ability to hose the entire machine
> >>> by trying to instantiate a virtual GIC.
> >> ...I don't see how your patch prevents instantiating a VGIC
> >> and hosing the machine on a system where the 64K
> >> with the GICV registers in it goes
> >> [GICV registers] [machine blows up if you read this]
> >> 0K 8K 64K
> > True, if such a machine existed, then this patch wouldn't detect it. I don't
> > think we support anything like that in mainline at the moment, but the
> > following additional diff should solve the problem, no?
> >
> > diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
> > index fa9a95b3ed19..476d3bf540a8 100644
> > --- a/virt/kvm/arm/vgic.c
> > +++ b/virt/kvm/arm/vgic.c
> > @@ -1539,6 +1539,14 @@ int kvm_vgic_hyp_init(void)
> > goto out_unmap;
> > }
> >
> > + if (!PAGE_ALIGNED(resource_size(&vcpu_res))) {
> > + kvm_err("GICV size 0x%llx not a multiple of page size 0x%lx\n",
> > + (unsigned long long)resource_size(&vcpu_res),
> > + PAGE_SIZE);
> > + ret = -ENXIO;
> > + goto out_unmap;
> > + }
> > +
> > vgic_vcpu_base = vcpu_res.start;
> >
> > kvm_info("%s@%llx IRQ%d\n", vgic_node->name,
> This would break with my SOC device tree which looks like this. Note
> this device tree works just fine without checks.
>
> gic: interrupt-controller@e1101000 {
> compatible = "arm,gic-400-v2m";
> #interrupt-cells = <3>;
> #address-cells = <0>;
> interrupt-controller;
> msi-controller;
> reg = <0x0 0xe1110000 0 0x1000>, /* gic dist */
> <0x0 0xe112f000 0 0x2000>, /* gic cpu */
> <0x0 0xe114f000 0 0x2000>, /* gic virtual ic*/
> <0x0 0xe116f000 0 0x2000>, /* gic virtual cpu*/
> <0x0 0xe1180000 0 0x1000>; /* gic msi */
> interrupts = <1 8 0xf04>;
> };
I appreciate it may work, but that's only because the kernel is actually
using an alias of GICV at 0xe1160000 by accident. I would say that you're
getting away with passing an incorrect description.
Will
next prev parent reply other threads:[~2014-07-25 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 19:27 [PATCH] kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform Will Deacon
2014-07-24 19:47 ` Peter Maydell
2014-07-24 19:55 ` Will Deacon
2014-07-24 20:01 ` Joel Schopp
2014-07-24 20:05 ` Peter Maydell
2014-07-25 9:31 ` Will Deacon
2014-07-25 10:06 ` Peter Maydell
2014-07-25 14:02 ` Joel Schopp
2014-07-25 14:08 ` Peter Maydell
2014-07-25 14:08 ` Will Deacon [this message]
2014-07-25 14:16 ` Joel Schopp
2014-07-25 14:23 ` Will Deacon
2014-07-25 14:59 ` Joel Schopp
2014-07-24 19:59 ` Joel Schopp
-- strict thread matches above, loose matches on Subject: below --
2014-07-30 12:55 [GIT PULL] KVM/ARM Urgent fix for 3.16 Christoffer Dall
2014-07-30 12:55 ` [PATCH] kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform 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=20140725140851.GJ5269@arm.com \
--to=will.deacon@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=ddutile@redhat.com \
--cc=gleb@kernel.org \
--cc=joel.schopp@amd.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=stable@vger.kernel.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