1. 06 10月, 2019 11 次提交
  2. 01 10月, 2019 26 次提交
  3. 30 9月, 2019 3 次提交
    • P
      Merge remote-tracking branch 'remotes/borntraeger/tags/s390x-20190930' into staging · 95e9d74f
      Peter Maydell 提交于
      - do not abuse memory_region_allocate_system_memory and split the memory
        according to KVM memslots in KVM code instead (Paolo, Igor)
      - change splitting to split at 4TB (Christian)
      - do not claim s390 (31bit) support in configure (Thomas)
      - sclp error checking (Janosch, Claudio)
      - new s390 pci maintainer (Matt, Collin)
      - fix s390 pci (again) (Matt)
      
      # gpg: Signature made Mon 30 Sep 2019 12:52:51 BST
      # gpg:                using RSA key 117BBC80B5A61C7C
      # gpg: Good signature from "Christian Borntraeger (IBM) <borntraeger@de.ibm.com>" [full]
      # Primary key fingerprint: F922 9381 A334 08F9 DBAB  FBCA 117B BC80 B5A6 1C7C
      
      * remotes/borntraeger/tags/s390x-20190930:
        s390/kvm: split kvm mem slots at 4TB
        s390: do not call memory_region_allocate_system_memory() multiple times
        kvm: split too big memory section on several memslots
        kvm: clear dirty bitmaps from all overlapping memslots
        kvm: extract kvm_log_clear_one_slot
        configure: Remove s390 (31-bit mode) from the list of supported CPUs
        s390x: sclp: Report insufficient SCCB length
        s390x: sclp: fix error handling for oversize control blocks
        s390x: sclp: boundary check
        s390x: sclp: refactor invalid command check
        s390: PCI: fix IOMMU region init
        MAINTAINERS: Update S390 PCI Maintainer
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      95e9d74f
    • C
      s390/kvm: split kvm mem slots at 4TB · c5b9ce51
      Christian Borntraeger 提交于
      Instead of splitting at an unaligned address, we can simply split at
      4TB.
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Acked-by: NIgor Mammedov <imammedo@redhat.com>
      c5b9ce51
    • I
      s390: do not call memory_region_allocate_system_memory() multiple times · fb1fc5a8
      Igor Mammedov 提交于
      s390 was trying to solve limited KVM memslot size issue by abusing
      memory_region_allocate_system_memory(), which breaks API contract
      where the function might be called only once.
      
      Beside an invalid use of API, the approach also introduced migration
      issue, since RAM chunks for each KVM_SLOT_MAX_BYTES are transferred in
      migration stream as separate RAMBlocks.
      
      After discussion [1], it was agreed to break migration from older
      QEMU for guest with RAM >8Tb (as it was relatively new (since 2.12)
      and considered to be not actually used downstream).
      Migration should keep working for guests with less than 8TB and for
      more than 8TB with QEMU 4.2 and newer binary.
      In case user tries to migrate more than 8TB guest, between incompatible
      QEMU versions, migration should fail gracefully due to non-exiting
      RAMBlock ID or RAMBlock size mismatch.
      
      Taking in account above and that now KVM code is able to split too
      big MemorySection into several memslots, partially revert commit
       (bb223055 s390-ccw-virtio: allow for systems larger that 7.999TB)
      and use kvm_set_max_memslot_size() to set KVMSlot size to
      KVM_SLOT_MAX_BYTES.
      
      1) [PATCH RFC v2 4/4] s390: do not call  memory_region_allocate_system_memory() multiple times
      Signed-off-by: NIgor Mammedov <imammedo@redhat.com>
      Message-Id: <20190924144751.24149-5-imammedo@redhat.com>
      Acked-by: NPeter Xu <peterx@redhat.com>
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      fb1fc5a8