diff options
author | Thomas Huth <thuth@redhat.com> | 2024-11-13 12:47:41 +0100 |
---|---|---|
committer | Thomas Huth <thuth@redhat.com> | 2024-11-18 10:54:42 +0100 |
commit | 6e7c96ae61e0542e97d385084f1f2281a0331054 (patch) | |
tree | 5800c07c1230dd871cfc025025e3a610c01c02c6 /include/hw/misc/stm32l4x5_exti.h | |
parent | b8c5fdc6588f82d95807be0eb2215d215a3ba16e (diff) | |
download | qemu-6e7c96ae61e0542e97d385084f1f2281a0331054.zip qemu-6e7c96ae61e0542e97d385084f1f2281a0331054.tar.gz qemu-6e7c96ae61e0542e97d385084f1f2281a0331054.tar.bz2 |
hw/s390x: Restrict "loadparm" property to devices that can be used for booting
Commit bb185de423 ("s390x: Add individual loadparm assignment to
CCW device") added a "loadparm" property to all CCW devices. This
was a little bit unfortunate, since this property is only useful
for devices that can be used for booting, but certainly it is not
useful for devices like virtio-gpu or virtio-tablet.
Thus let's restrict the property to CCW devices that we can boot from
(i.e. virtio-block, virtio-net and vfio-ccw devices).
Message-ID: <20241113114741.681096-1-thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Jared Rossi <jrossi@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'include/hw/misc/stm32l4x5_exti.h')
0 files changed, 0 insertions, 0 deletions