KVM: s390: fix mismatch between user and in-kernel guest limit
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>
Showing
- Documentation/virtual/kvm/devices/vm.txt 2 additions, 1 deletionDocumentation/virtual/kvm/devices/vm.txt
- arch/s390/include/asm/kvm_host.h 1 addition, 0 deletionsarch/s390/include/asm/kvm_host.h
- arch/s390/include/uapi/asm/kvm.h 2 additions, 0 deletionsarch/s390/include/uapi/asm/kvm.h
- arch/s390/kvm/kvm-s390.c 20 additions, 5 deletionsarch/s390/kvm/kvm-s390.c
- arch/s390/mm/pgtable.c 2 additions, 2 deletionsarch/s390/mm/pgtable.c
Please register or sign in to comment