KVM: s390: fix mismatch between user and in-kernel guest limit

Browse source

While the userspace interface requests the maximum size the gmap code
expects to get a maximum address.

This error resulted in bigger page tables than necessary for some guest
sizes, e.g. a 2GB guest used 3 levels instead of 2.

At the same time we introduce KVM_S390_NO_MEM_LIMIT, which allows in a
bright future that a guest spans the complete 64 bit address space.

We also switch to TASK_MAX_SIZE for the initial memory size, this is a
cosmetic change as the previous size also resulted in a 4 level pagetable
creation.

Reported-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Dominik Dingel <dingel@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>

...

This commit is contained in:

Dominik Dingel 2014-12-01 17:24:42 +01:00 • committed by Christian Borntraeger

parent 8335713ad0

commit a3a92c31bf

5 changed files with 27 additions and 8 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

Documentation/virtual/kvm/devices/vm.txt

View file

1

arch/s390/include/asm/kvm_host.h

View file

2

arch/s390/include/uapi/asm/kvm.h

View file

25

arch/s390/kvm/kvm-s390.c

View file

4

arch/s390/mm/pgtable.c

View file