3df4843d0e
The SCLP boundary cross check is done by the Ultravisor for a
protected guest, hence we don't need to do it. As QEMU doesn't get a
valid SCCB address in protected mode this is even problematic and can
lead to QEMU reporting a false boundary cross error.
Fixes:
|
||
---|---|---|
.. | ||
3270-ccw.c | ||
ap-bridge.c | ||
ap-device.c | ||
ccw-device.c | ||
ccw-device.h | ||
css-bridge.c | ||
css.c | ||
event-facility.c | ||
ipl.c | ||
ipl.h | ||
Kconfig | ||
meson.build | ||
pv.c | ||
s390-ccw.c | ||
s390-pci-bus.c | ||
s390-pci-bus.h | ||
s390-pci-inst.c | ||
s390-pci-inst.h | ||
s390-skeys-kvm.c | ||
s390-skeys.c | ||
s390-stattrib-kvm.c | ||
s390-stattrib.c | ||
s390-virtio-ccw.c | ||
s390-virtio-hcall.c | ||
s390-virtio-hcall.h | ||
sclp.c | ||
sclpcpu.c | ||
sclpquiesce.c | ||
tod-kvm.c | ||
tod-qemu.c | ||
tod.c | ||
trace-events | ||
trace.h | ||
vhost-user-fs-ccw.c | ||
vhost-vsock-ccw.c | ||
virtio-ccw-9p.c | ||
virtio-ccw-balloon.c | ||
virtio-ccw-blk.c | ||
virtio-ccw-crypto.c | ||
virtio-ccw-gpu.c | ||
virtio-ccw-input.c | ||
virtio-ccw-net.c | ||
virtio-ccw-rng.c | ||
virtio-ccw-scsi.c | ||
virtio-ccw-serial.c | ||
virtio-ccw.c | ||
virtio-ccw.h |