diff options
author | Marc Zyngier <marc.zyngier@arm.com> | 2016-04-05 18:11:47 +0300 |
---|---|---|
committer | Christoffer Dall <christoffer.dall@linaro.org> | 2016-04-06 14:33:14 +0300 |
commit | 6141570c36f0c937d5deff20d9cf08cbd8d8ed48 (patch) | |
tree | 321db1eba7dba333aed3b4f22305c02227ff3038 /drivers/regulator/pfuze100-regulator.c | |
parent | 1c5631c73fc2261a5df64a72c155cb53dcdc0c45 (diff) | |
download | linux-6141570c36f0c937d5deff20d9cf08cbd8d8ed48.tar.xz |
arm64: KVM: Warn when PARange is less than 40 bits
We always thought that 40bits of PA range would be the minimum people
would actually build. Anything less is terrifyingly small.
Turns out that we were both right and wrong. Nobody has ever built
such a system, but the ARM Foundation Model has a PARange set to 36bits.
Just because we can. Oh well. Now, the KVM API explicitely says that
we offer a 40bit PA space to the VM, so we shouldn't run KVM on
the Foundation Model at all.
That being said, this patch offers a less agressive alternative, and
loudly warns about the configuration being unsupported. You'll still
be able to run VMs (at your own risks, though).
This is just a workaround until we have a proper userspace API where
we report the PARange to userspace.
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Diffstat (limited to 'drivers/regulator/pfuze100-regulator.c')
0 files changed, 0 insertions, 0 deletions