[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-1
From: |
Stefan Hajnoczi |
Subject: |
Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18 |
Date: |
Wed, 18 Dec 2024 16:09:35 -0500 |
On Wed, 18 Dec 2024 at 05:55, David Hildenbrand <david@redhat.com> wrote:
>
> The following changes since commit 8032c78e556cd0baec111740a6c636863f9bd7c8:
>
> Merge tag 'firmware-20241216-pull-request' of
> https://gitlab.com/kraxel/qemu into staging (2024-12-16 14:20:33 -0500)
>
> are available in the Git repository at:
>
> https://github.com/davidhildenbrand/qemu.git tags/mem-2024-12-18
>
> for you to fetch changes up to eb5c5f1ab479e9311d8e513e3eeafaf30f2b25b3:
>
> s390x: virtio-mem support (2024-12-18 09:50:05 +0100)
>
> ----------------------------------------------------------------
> Hi,
>
> "Host Memory Backends" and "Memory devices" queue ("mem"):
> - Fixup handling of virtio-mem unplug during system resets, as
> preparation for s390x support (especially kdump in the Linux guest)
> - virtio-mem support for s390x
>
> ----------------------------------------------------------------
> David Hildenbrand (15):
> virtio-mem: unplug memory only during system resets, not device resets
> s390x/s390-virtio-ccw: don't crash on weird RAM sizes
> s390x/s390-virtio-hcall: remove hypercall registration mechanism
> s390x/s390-virtio-hcall: prepare for more diag500 hypercalls
> s390x: rename s390-virtio-hcall* to s390-hypercall*
> s390x/s390-virtio-ccw: move setting the maximum guest size from sclp to
> machine code
> s390x: introduce s390_get_memory_limit()
> s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT
> s390x/s390-stattrib-kvm: prepare for memory devices and sparse memory
> layouts
> s390x/s390-skeys: prepare for memory devices
> s390x/s390-virtio-ccw: prepare for memory devices
> s390x/pv: prepare for memory devices
> s390x: remember the maximum page size
> s390x/virtio-ccw: add support for virtio based memory devices
> s390x: virtio-mem support
Please take a look at the following s390x-related CI failures:
https://gitlab.com/qemu-project/qemu/-/jobs/8679972861
https://gitlab.com/qemu-project/qemu/-/jobs/8679972809
https://gitlab.com/qemu-project/qemu/-/jobs/8679972809
https://gitlab.com/qemu-project/qemu/-/jobs/8679972912
https://gitlab.com/qemu-project/qemu/-/jobs/8679972894
https://gitlab.com/qemu-project/qemu/-/jobs/8679972931
If you find that this pull request caused the issue, please send a new
revision of the pull request. Thanks!
Stefan
>
> MAINTAINERS | 5 +
> hw/s390x/Kconfig | 1 +
> hw/s390x/meson.build | 6 +-
> hw/s390x/s390-hypercall.c | 85 ++++++++++++++
> hw/s390x/s390-hypercall.h | 25 ++++
> hw/s390x/s390-skeys.c | 6 +-
> hw/s390x/s390-stattrib-kvm.c | 67 +++++++----
> hw/s390x/s390-virtio-ccw.c | 165 ++++++++++++++++++---------
> hw/s390x/s390-virtio-hcall.c | 41 -------
> hw/s390x/s390-virtio-hcall.h | 25 ----
> hw/s390x/sclp.c | 17 +--
> hw/s390x/virtio-ccw-md-stubs.c | 24 ++++
> hw/s390x/virtio-ccw-md.c | 153 +++++++++++++++++++++++++
> hw/s390x/virtio-ccw-md.h | 44 ++++++++
> hw/s390x/virtio-ccw-mem.c | 226
> +++++++++++++++++++++++++++++++++++++
> hw/s390x/virtio-ccw-mem.h | 34 ++++++
> hw/virtio/Kconfig | 1 +
> hw/virtio/virtio-mem.c | 107 ++++++++++++------
> include/hw/s390x/s390-virtio-ccw.h | 4 +
> include/hw/virtio/virtio-mem.h | 13 ++-
> target/s390x/cpu-sysemu.c | 15 ---
> target/s390x/cpu.h | 2 -
> target/s390x/kvm/kvm.c | 18 +--
> target/s390x/kvm/pv.c | 2 +-
> target/s390x/tcg/misc_helper.c | 7 +-
> 25 files changed, 866 insertions(+), 227 deletions(-)
> create mode 100644 hw/s390x/s390-hypercall.c
> create mode 100644 hw/s390x/s390-hypercall.h
> delete mode 100644 hw/s390x/s390-virtio-hcall.c
> delete mode 100644 hw/s390x/s390-virtio-hcall.h
> create mode 100644 hw/s390x/virtio-ccw-md-stubs.c
> create mode 100644 hw/s390x/virtio-ccw-md.c
> create mode 100644 hw/s390x/virtio-ccw-md.h
> create mode 100644 hw/s390x/virtio-ccw-mem.c
> create mode 100644 hw/s390x/virtio-ccw-mem.h
> --
> 2.47.1
>
>
- [PULL 12/15] s390x/pv: prepare for memory devices, (continued)
- [PULL 12/15] s390x/pv: prepare for memory devices, David Hildenbrand, 2024/12/18
- [PULL 01/15] virtio-mem: unplug memory only during system resets, not device resets, David Hildenbrand, 2024/12/18
- [PULL 10/15] s390x/s390-skeys: prepare for memory devices, David Hildenbrand, 2024/12/18
- [PULL 14/15] s390x/virtio-ccw: add support for virtio based memory devices, David Hildenbrand, 2024/12/18
- [PULL 03/15] s390x/s390-virtio-hcall: remove hypercall registration mechanism, David Hildenbrand, 2024/12/18
- [PULL 15/15] s390x: virtio-mem support, David Hildenbrand, 2024/12/18
- [PULL 04/15] s390x/s390-virtio-hcall: prepare for more diag500 hypercalls, David Hildenbrand, 2024/12/18
- [PULL 06/15] s390x/s390-virtio-ccw: move setting the maximum guest size from sclp to machine code, David Hildenbrand, 2024/12/18
- [PULL 09/15] s390x/s390-stattrib-kvm: prepare for memory devices and sparse memory layouts, David Hildenbrand, 2024/12/18
- [PULL 07/15] s390x: introduce s390_get_memory_limit(), David Hildenbrand, 2024/12/18
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18,
Stefan Hajnoczi <=
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, David Hildenbrand, 2024/12/18
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, David Hildenbrand, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, Philippe Mathieu-Daudé, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, David Hildenbrand, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, David Hildenbrand, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, Philippe Mathieu-Daudé, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, David Hildenbrand, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, Philippe Mathieu-Daudé, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, Christian Borntraeger, 2024/12/19
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, David Hildenbrand, 2024/12/19