[prev in list] [next in list] [prev in thread] [next in thread] 

List:       qemu-ppc
Subject:    [Qemu-ppc] [PATCH v2 0/2] s390x/kvm: Properly detect page size of initial memory
From:       David Hildenbrand <david () redhat ! com>
Date:       2019-03-28 11:34:56
Message-ID: 20190328113458.8405-1-david () redhat ! com
[Download RAW message or body]

This is based on the patch
    [PATCH for-4.0?] exec: Only count mapped memory backends for
    qemu_getrampagesize()

While the detection on s390x of the maximum ram pagesize works by pure luck,
we should try to do better. Especially, once "-mem-path" is replaced
by memory backends, the current approach will break.

Configure the maximum page size after configuring initital memory. Provide
a function to detect the maximum ram pagesize

I think this can be deferred to 4.1 as I don't think anything is actually
broken right now.

v1 -> v2:
- Add a better comment describing that only initial memory is considered
- Add "exec: Introduce qemu_getmaxrampagesize() and rename
  qemu_getrampagesize()"

David Hildenbrand (2):
  s390x/kvm: Configure page size after memory has actually been
    initialized
  exec: Introduce qemu_getmaxrampagesize() and rename
    qemu_getrampagesize()

 exec.c                     | 39 ++++++++++++++++++++++++++++++++++----
 hw/ppc/spapr_caps.c        |  4 ++--
 hw/s390x/s390-virtio-ccw.c | 12 ++++++++++++
 hw/vfio/spapr.c            |  2 +-
 target/ppc/kvm.c           |  2 +-
 target/s390x/cpu.c         |  7 +++++++
 target/s390x/cpu.h         |  1 +
 target/s390x/kvm-stub.c    |  4 ++++
 target/s390x/kvm.c         | 35 ++++++++++++++--------------------
 target/s390x/kvm_s390x.h   |  1 +
 10 files changed, 78 insertions(+), 29 deletions(-)

-- 
2.17.2



[prev in list] [next in list] [prev in thread] [next in thread]