1fa755234e
virtio-ccw has an odd sequence of realizing devices: first the device-specific relization (net, block, ...), then the generic realization. It feels less odd to have the generic realization callback trigger the device-specific realization instead (and this also matches what virtio-pci does). One thing to note: We need to defer initializing the cu model in the sense id data until after the device-specific realization has been performed, as we need to refer to the virtio device's device_id. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> Message-Id: <1429627016-30656-2-git-send-email-cornelia.huck@de.ibm.com> |
||
|---|---|---|
| .. | ||
| css.c | ||
| css.h | ||
| event-facility.c | ||
| ipl.c | ||
| ipl.h | ||
| Makefile.objs | ||
| s390-pci-bus.c | ||
| s390-pci-bus.h | ||
| s390-pci-inst.c | ||
| s390-pci-inst.h | ||
| s390-virtio-bus.c | ||
| s390-virtio-bus.h | ||
| s390-virtio-ccw.c | ||
| s390-virtio-hcall.c | ||
| s390-virtio.c | ||
| s390-virtio.h | ||
| sclp.c | ||
| sclpcpu.c | ||
| sclpquiesce.c | ||
| virtio-ccw.c | ||
| virtio-ccw.h | ||