Full list (based on the merge the mentioned commit is part of) seems to
be:
aa910c20ec5 s390x: virtio-mem support
88d86f6f1e3 s390x/virtio-ccw: add support for virtio based memory devices
df2ac211a62 s390x: remember the maximum page size
a056332e732 s390x/pv: prepare for memory devices
1e86400298c s390x/s390-virtio-ccw: prepare for memory devices
d1e3c2ac41b s390x/s390-skeys: prepare for memory devices
241e6b2d27b s390x/s390-stattrib-kvm: prepare for memory devices and sparse
memory layouts
f7c16865781 s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT
27221b69a3e s390x: introduce s390_get_memory_limit()
3c6fb557d29 s390x/s390-virtio-ccw: move setting the maximum guest size from
sclp to machine code
85489fc3652 s390x: rename s390-virtio-hcall* to s390-hypercall*
6e9cc2da4e8 s390x/s390-virtio-hcall: prepare for more diag500 hypercalls
4be0fce498d s390x/s390-virtio-hcall: remove hypercall registration mechanism
14e568ab483 s390x/s390-virtio-ccw: don't crash on weird RAM sizes
713484d0389 virtio-mem: unplug memory only during system resets, not device
resets
They applied fine, I'll see at build time if there are obvious dependent
changes.
I did not find any subsequent fixes/reverts of any of those.
If any "oh wait, you should know ..." comes to your mind let me know.
** Changed in: qemu (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097884
Title:
[25.04 FEAT] [VS2027] KVM: Enable virtio-mem support - qemu part
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2097884/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
