diff options
author | Marc Zyngier <marc.zyngier@arm.com> | 2015-03-10 19:07:00 +0000 |
---|---|---|
committer | Christoffer Dall <christoffer.dall@linaro.org> | 2015-03-11 14:24:36 +0100 |
commit | 04b8dc85bf4a64517e3cf20e409eeaa503b15cc1 (patch) | |
tree | ce074a61824c768147f911152c4af6dfa97ff9eb /kernel/up.c | |
parent | a987370f8e7a1677ae385042644326d9cd145a20 (diff) | |
download | linux-04b8dc85bf4a64517e3cf20e409eeaa503b15cc1.tar.gz |
arm64: KVM: Do not use pgd_index to index stage-2 pgd
The kernel's pgd_index macro is designed to index a normal, page
sized array. KVM is a bit diffferent, as we can use concatenated
pages to have a bigger address space (for example 40bit IPA with
4kB pages gives us an 8kB PGD.
In the above case, the use of pgd_index will always return an index
inside the first 4kB, which makes a guest that has memory above
0x8000000000 rather unhappy, as it spins forever in a page fault,
whist the host happilly corrupts the lower pgd.
The obvious fix is to get our own kvm_pgd_index that does the right
thing(tm).
Tested on X-Gene with a hacked kvmtool that put memory at a stupidly
high address.
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Diffstat (limited to 'kernel/up.c')
0 files changed, 0 insertions, 0 deletions