Re: [PATCH v3 0/7] virtio-mem: s390 support

[Eric Farman <farman@linux.ibm.com>]

On Wed, 2024-10-30 at 17:49 +0100, Christian Borntraeger wrote:
> 
> Am 30.10.24 um 10:34 schrieb Heiko Carstens:
> > On Fri, Oct 25, 2024 at 04:14:45PM +0200, David Hildenbrand wrote:
> > > Let's finally add s390 support for virtio-mem; my last RFC was sent
> > > 4 years ago, and a lot changed in the meantime.
> > > 
> > > The latest QEMU series is available at [1], which contains some more
> > > details and a usage example on s390 (last patch).
> > > 
> > > There is not too much in here: The biggest part is querying a new diag(500)
> > > STORAGE_LIMIT hypercall to obtain the proper "max_physmem_end".
> > 
> > ...
> > 
> > > David Hildenbrand (7):
> > >    Documentation: s390-diag.rst: make diag500 a generic KVM hypercall
> > >    Documentation: s390-diag.rst: document diag500(STORAGE LIMIT)
> > >      subfunction
> > >    s390/physmem_info: query diag500(STORAGE LIMIT) to support QEMU/KVM
> > >      memory devices
> > >    virtio-mem: s390 support
> > >    lib/Kconfig.debug: default STRICT_DEVMEM to "y" on s390
> > >    s390/sparsemem: reduce section size to 128 MiB
> > >    s390/sparsemem: provide memory_add_physaddr_to_nid() with CONFIG_NUMA
> > > 
> > >   Documentation/virt/kvm/s390/s390-diag.rst | 35 +++++++++++++----
> > >   arch/s390/boot/physmem_info.c             | 47 ++++++++++++++++++++++-
> > >   arch/s390/boot/startup.c                  |  7 +++-
> > >   arch/s390/include/asm/physmem_info.h      |  3 ++
> > >   arch/s390/include/asm/sparsemem.h         | 10 ++++-
> > >   drivers/virtio/Kconfig                    | 12 +++---
> > >   lib/Kconfig.debug                         |  2 +-
> > >   7 files changed, 98 insertions(+), 18 deletions(-)
> > 
> > I'll apply the whole series as soon as there are ACKs for the third
> > patch, and from the KVM guys for the whole series.
> > Christian, Janosch, Claudio?
> 
> Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
> for the series.
> 
> @Eric Farman,
> Was someone from your team planning to look into this (testing, review whatever)?

The guy that was testing it just got back from a long holiday. I'll ping him and see if he can chime
in here.