KVM: s390: Remove the sanity checks for kvm memory slot

To model the standby memory with memory_region_add_subregion
and friends, the guest would have one or more regions of ram.
Remove the check allowing only one memory slot and the check
requiring the real address of memory slot starts at zero.

Signed-off-by: Nick Wang <jfwang@us.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Gleb Natapov <gleb@redhat.com>

diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
index d05a59c1eea727eb624a3fcde1f8f440d10cd6fb..b322ff15751d5051551f6fcb1c7cde1c5240996d 100644 (file)
--- a/arch/s390/kvm/kvm-s390.c
+++ b/arch/s390/kvm/kvm-s390.c
@@ -977,18 +977,10 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm,
                                   struct kvm_userspace_memory_region *mem,
                                   enum kvm_mr_change change)
 {
-       /* A few sanity checks. We can have exactly one memory slot which has
-          to start at guest virtual zero and which has to be located at a
-          page boundary in userland and which has to end at a page boundary.
-          The memory in userland is ok to be fragmented into various different
-          vmas. It is okay to mmap() and munmap() stuff in this slot after
-          doing this call at any time */
-
-       if (mem->slot)
-               return -EINVAL;
-
-       if (mem->guest_phys_addr)
-               return -EINVAL;
+       /* A few sanity checks. We can have memory slots which have to be
+          located/ended at a segment boundary (1MB). The memory in userland is
+          ok to be fragmented into various different vmas. It is okay to mmap()
+          and munmap() stuff in this slot after doing this call at any time */
 
        if (mem->userspace_addr & 0xffffful)
                return -EINVAL;