Searched hist:"68 d00e429395a273cf25827f89f036548fb67bdd" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/monitor/ |
| H A D | qmp-cmds.c | diff 68d00e429395a273cf25827f89f036548fb67bdd Thu Jun 06 10:41:30 CDT 2019 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> block/block-backend: blk_iostatus_reset: drop usage of bs->job
We are going to remove bs->job pointer. Drop it's usage in
blk_iostatus_reset.
blk_iostatus_reset() has only two callers:
1. blk_attach_dev(). This doesn't have anything to do with jobs and
attaching a new guest device won't solve any problem the job
encountered, so no reason to reset the iostatus for the job.
2. qmp_cont(). This resets the iostatus for everything. We can just
call block_job_iostatus_reset() for all block jobs instead of going
through BlockBackend.
Suggested-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
| /openbmc/qemu/block/ |
| H A D | block-backend.c | diff 68d00e429395a273cf25827f89f036548fb67bdd Thu Jun 06 10:41:30 CDT 2019 Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> block/block-backend: blk_iostatus_reset: drop usage of bs->job
We are going to remove bs->job pointer. Drop it's usage in
blk_iostatus_reset.
blk_iostatus_reset() has only two callers:
1. blk_attach_dev(). This doesn't have anything to do with jobs and
attaching a new guest device won't solve any problem the job
encountered, so no reason to reset the iostatus for the job.
2. qmp_cont(). This resets the iostatus for everything. We can just
call block_job_iostatus_reset() for all block jobs instead of going
through BlockBackend.
Suggested-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|