From: christoffer.dall@arm.com (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: drop resource size check for GICV window
Date: Sat, 9 Jun 2018 13:20:47 +0200 [thread overview]
Message-ID: <20180609112047.GK5097@C02W217FHV2R.local> (raw)
In-Reply-To: <1559C9EA-DE8B-4F96-8406-CCBEB0DFD093@linaro.org>
On Sat, Jun 09, 2018 at 12:30:14PM +0200, Ard Biesheuvel wrote:
>
>
> > On 9 Jun 2018, at 12:06, Christoffer Dall <christoffer.dall@arm.com> wrote:
> >
> >> On Fri, Jun 01, 2018 at 05:06:28PM +0200, Ard Biesheuvel wrote:
> >> When booting a 64 KB pages kernel on a ACPI GICv3 system that
> >> implements support for v2 emulation, the following warning is
> >> produced
> >>
> >> GICV size 0x2000 not a multiple of page size 0x10000
> >>
> >> and support for v2 emulation is disabled, preventing GICv2 VMs
> >> from being able to run on such hosts.
> >>
> >> The reason is that vgic_v3_probe() performs a sanity check on the
> >> size of the window (it should be a multiple of the page size),
> >> while the ACPI MADT parsing code hardcodes the size of the window
> >> to 8 KB. This makes sense, considering that ACPI does not bother
> >> to describe the size in the first place, under the assumption that
> >> platforms implementing ACPI will follow the architecture and not
> >> put anything else in the same 64 KB window.
> >
> > Does the architecture actually say that anywhere?
> >
> >>
> >> So let's just drop the sanity check altogether, and assume that
> >> the window is at least 64 KB in size.
> >
> > This could obviously be dangerous if broken systems actually exist.
> > Marc may know more about that than me. An alternative would be to
> > modify the ACPI code to assume max(8 KB, page size) instead, and/or a
> > command line parameter to override this check.
> >
> > That said, I'm not directly opposed to this patch, but I'll let Marc
> > have a look as well.
> >
>
> This approach was actually Marc?s idea, and he already applied the patch to the queue branch afaik.
>
Hmmm, ok.
-Christoffer
next prev parent reply other threads:[~2018-06-09 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 15:06 [PATCH] KVM: arm/arm64: drop resource size check for GICV window Ard Biesheuvel
2018-06-09 10:06 ` Christoffer Dall
2018-06-09 10:30 ` Ard Biesheuvel
2018-06-09 11:20 ` Christoffer Dall [this message]
2018-06-09 12:09 ` Marc Zyngier
2018-06-09 18:58 ` 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=20180609112047.GK5097@C02W217FHV2R.local \
--to=christoffer.dall@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