diff options
author | Stefan Hajnoczi <stefanha@redhat.com> | 2014-03-20 15:06:32 +0100 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2014-04-04 20:48:13 +0200 |
commit | 54bee5c2b487250dcb8631ddff4307f329ec0541 (patch) | |
tree | 611313e4e7b49a4a04a94b297df92f0382db3921 /hw/watchdog | |
parent | 8c2664d86917c987944f1ca9770d1f7bbbf8eca8 (diff) | |
download | hqemu-54bee5c2b487250dcb8631ddff4307f329ec0541.zip hqemu-54bee5c2b487250dcb8631ddff4307f329ec0541.tar.gz |
dataplane: replace iothread object_add() with embedded instance
Before IOThread was its own object, each virtio-blk device would create
its own internal thread. We need to preserve this behavior for
backwards compatibility when users do not specify -device
virtio-blk-pci,iothread=<id>.
This patch changes how the internal IOThread object is created.
Previously we used the monitor object_add() function, which is really a
layering violation. The problem is that this needs to assign a name but
we don't have a name for this internal object.
Generating names for internal objects is a pain but even worse is that
they may collide with user-defined names.
Paolo Bonzini <pbonzini@redhat.com> suggested that the internal IOThread
object should not be named. This way the conflict cannot happen and we
no longer need object_add().
One gotcha is that internal IOThread objects will not be listed by the
query-iothreads command since they are not named. This is okay though
because query-iothreads is new and the internal IOThread is just for
backwards compatibility. New users should explicitly define IOThread
objects.
Reported-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'hw/watchdog')
0 files changed, 0 insertions, 0 deletions