| commit | 1fa755234e24697cc76f326782edbb09bd0a3a53 | |
| author | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Tue, 21 Apr 2015 14:36:55 +0000 (21 16:36 +0200) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Fri, 8 May 2015 08:36:02 +0000 (8 10:36 +0200) | ||
| tree | df89f5737993aeb9268dc60f9b0322e83b633493 | treesnapshot (tar.gz zip) |
| parent | 77ae0b2a6e731ab7b97e9fae401c579397edb31c | commitdiff |
virtio-ccw: change realization sequence
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>
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>
| hw/s390x/virtio-ccw.c | diffblobblamehistory |