From: Joel Schopp <joel.schopp@amd.com>
To: Will Deacon <will.deacon@arm.com>, <pbonzini@redhat.com>,
<gleb@kernel.org>
Cc: <peter.maydell@linaro.org>, <kvmarm@lists.cs.columbia.edu>,
<kvm@vger.kernel.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
"Marc Zyngier" <marc.zyngier@arm.com>,
Don Dutile <ddutile@redhat.com>
Subject: Re: [PATCH v2] kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform
Date: Fri, 25 Jul 2014 10:56:18 -0500 [thread overview]
Message-ID: <53D27E22.2050602@amd.com> (raw)
In-Reply-To: <1406302152-32335-1-git-send-email-will.deacon@arm.com>
On 07/25/2014 10:29 AM, Will Deacon wrote:
> If the physical address of GICV isn't page-aligned, then we end up
> creating a stage-2 mapping of the page containing it, which causes us to
> map neighbouring memory locations directly into the guest.
>
> As an example, consider a platform with GICV at physical 0x2c02f000
> running a 64k-page host kernel. If qemu maps this into the guest at
> 0x80010000, then guest physical addresses 0x80010000 - 0x8001efff will
> map host physical region 0x2c020000 - 0x2c02efff. Accesses to these
> physical regions may cause UNPREDICTABLE behaviour, for example, on the
> Juno platform this will cause an SError exception to EL3, which brings
> down the entire physical CPU resulting in RCU stalls / HYP panics / host
> crashing / wasted weeks of debugging.
No denying this is a problem.
>
> SBSA recommends that systems alias the 4k GICV across the bounding 64k
> region, in which case GICV physical could be described as 0x2c020000 in
> the above scenario.
The problem with this patch is the gicv is really 8K. The reason you
would map at a 60K offset (0xf000), and why we do on our SOC, is so that
the 8K gicv would pick up the last 4K from the first page and the first
4K from the next page. With your patch it is impossible to map all 8K
of the gicv with 64K pages.
My SOC which works fine with kvm now will go to not working with kvm
after this patch.
>
> This patch fixes the problem by failing the vgic probe if the physical
> base address or the size of GICV aren't page-aligned. Note that this
> generated a warning in dmesg about freeing enabled IRQs, so I had to
> move the IRQ enabling later in the probe.
>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Gleb Natapov <gleb@kernel.org>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Joel Schopp <joel.schopp@amd.com>
> Cc: Don Dutile <ddutile@redhat.com>
> Acked-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---
>
> v1 ->v2 : Added size alignment check and Peter's ack. Could this go in
> for 3.16 please?
>
> virt/kvm/arm/vgic.c | 24 ++++++++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
> index 56ff9bebb577..476d3bf540a8 100644
> --- a/virt/kvm/arm/vgic.c
> +++ b/virt/kvm/arm/vgic.c
> @@ -1526,17 +1526,33 @@ int kvm_vgic_hyp_init(void)
> goto out_unmap;
> }
>
> - kvm_info("%s@%llx IRQ%d\n", vgic_node->name,
> - vctrl_res.start, vgic_maint_irq);
> - on_each_cpu(vgic_init_maintenance_interrupt, NULL, 1);
> -
> if (of_address_to_resource(vgic_node, 3, &vcpu_res)) {
> kvm_err("Cannot obtain VCPU resource\n");
> ret = -ENXIO;
> goto out_unmap;
> }
> +
> + if (!PAGE_ALIGNED(vcpu_res.start)) {
> + kvm_err("GICV physical address 0x%llx not page aligned\n",
> + (unsigned long long)vcpu_res.start);
> + ret = -ENXIO;
> + 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,
> + vctrl_res.start, vgic_maint_irq);
> + on_each_cpu(vgic_init_maintenance_interrupt, NULL, 1);
> +
> goto out;
>
> out_unmap:
next prev parent reply other threads:[~2014-07-25 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 15:29 [PATCH v2] kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform Will Deacon
2014-07-25 15:56 ` Joel Schopp [this message]
2014-07-25 16:02 ` Peter Maydell
2014-07-25 16:24 ` Joel Schopp
2014-07-25 16:38 ` Will Deacon
2014-07-25 16:09 ` Will Deacon
2014-07-30 10:47 ` Marc Zyngier
2014-07-30 12:55 ` 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=53D27E22.2050602@amd.com \
--to=joel.schopp@amd.com \
--cc=christoffer.dall@linaro.org \
--cc=ddutile@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=will.deacon@arm.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