| commit | 0be63901d2a33a6ed25caa5df3f530df75338f6a | |
| author | Gonglei <arei.gonglei@huawei.com> | |
| Thu, 29 Jan 2015 07:08:51 +0000 (29 15:08 +0800) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Wed, 11 Feb 2015 20:47:51 +0000 (11 21:47 +0100) | ||
| tree | 646c8bc5c70c485cd6db1ab64f295c6875f6621c | treesnapshot (tar.gz zip) |
| parent | edecf5eced082cb45e213cb4e791b2fcf9f867c1 | commitdiff |
qdev: support to get a device firmware path directly
commit 6b1566c (qdev: Introduce FWPathProvider interface) did a
good job for supproting to get firmware path on some different
architectures.
Moreover further more, we can use the interface to get firmware
path name for a device which isn't attached a specific bus,
such as virtio-bus, scsi-bus etc.
When the device (such as vhost-scsi) realize the TYPE_FW_PATH_PROVIDER
interface, we should introduce a new function to get the correct firmware
path name for it.
Signed-off-by: Gonglei <arei.gonglei@huawei.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
commit 6b1566c (qdev: Introduce FWPathProvider interface) did a
good job for supproting to get firmware path on some different
architectures.
Moreover further more, we can use the interface to get firmware
path name for a device which isn't attached a specific bus,
such as virtio-bus, scsi-bus etc.
When the device (such as vhost-scsi) realize the TYPE_FW_PATH_PROVIDER
interface, we should introduce a new function to get the correct firmware
path name for it.
Signed-off-by: Gonglei <arei.gonglei@huawei.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| bootdevice.c | diffblobblamehistory | |
| hw/core/qdev.c | diffblobblamehistory | |
| include/hw/qdev-core.h | diffblobblamehistory |