Message ID | 20210903155514.44772-1-david@redhat.com |
---|---|
Headers | show |
Series | s390x: skey related fixes, cleanups, and memory device preparations | expand |
On 03/09/2021 17.55, David Hildenbrand wrote: > This series fixes multiple TCG issues related to storage key instructions, > fixes some TCG issues related to LOAD REAL ADDRESS and skeys, implements > lazy skey enablement under TCG, and prepares the whole skey infrastructure > for dealing with addresses beyond initial RAM (e.g., memory devices like > virtio-mem). Along, some cleanups. > > To prepare for memory devices / memory hotplug, my goal was to get rid of > as many ms->ram_size users as possible. Unfortunately, I stumbled over > many other things on the way. The remaining s390x users of ms->ram_size > are: > > a) hw/s390x/ipl.c: loading the FW. Won't need adjustment. > b) hw/s390x/s390-skeys.c: allocating the array for storage keys. Will need > adjustment for memory devices. > c) hw/s390x/s390-stattrib-kvm.c: will need adjustments in the future when > using memory devices with CMM. > d) hw/s390x/s390-virtio-ccw.c: fixing up / handling initital ram. Won't > need adjustment. > e) hw/s390x/sclp.c: same as d) > > Especially patch 9-12 also affect KVM. The remaining ones mostly only > affect TCG. Thanks, applied to my s390x-next branch: https://gitlab.com/thuth/qemu/-/commits/s390x-next/ Thomas