diff options
| author | Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> | 2019-06-06 18:41:32 +0300 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2019-06-18 16:41:10 +0200 |
| commit | b23c580c946644b906af36e3f903b9fedd6ccd61 (patch) | |
| tree | fd1da098448077b498db94f12df9a1d3aa411b32 /block/trace-events | |
| parent | 8164102ffe02dfc6478c0b3f8ffce29705a9a53b (diff) | |
| download | qemu-b23c580c946644b906af36e3f903b9fedd6ccd61.zip qemu-b23c580c946644b906af36e3f903b9fedd6ccd61.tar.gz qemu-b23c580c946644b906af36e3f903b9fedd6ccd61.tar.bz2 | |
block: drop bs->job
Drop remaining users of bs->job:
1. assertions actually duplicated by assert(!bs->refcnt)
2. trace-point seems not enough reason to change stream_start to return
BlockJob pointer
3. Restricting creation of two jobs based on same bs is bad idea, as
3.1 Some jobs creates filters to be their main node, so, this check
don't actually prevent creating second job on same real node (which
will create another filter node) (but I hope it is restricted by
other mechanisms)
3.2 Even without bs->job we have two systems of permissions:
op-blockers and BLK_PERM
3.3 We may want to run several jobs on one node one day
And finally, drop bs->job pointer itself. Hurrah!
Suggested-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block/trace-events')
| -rw-r--r-- | block/trace-events | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/block/trace-events b/block/trace-events index f6e43ee..9ccea75 100644 --- a/block/trace-events +++ b/block/trace-events @@ -53,7 +53,7 @@ qmp_block_job_resume(void *job) "job %p" qmp_block_job_complete(void *job) "job %p" qmp_block_job_finalize(void *job) "job %p" qmp_block_job_dismiss(void *job) "job %p" -qmp_block_stream(void *bs, void *job) "bs %p job %p" +qmp_block_stream(void *bs) "bs %p" # file-posix.c # file-win32.c |