[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v5 00/21] blockjobs: add explicit job management
From: |
Kevin Wolf |
Subject: |
Re: [Qemu-devel] [PATCH v5 00/21] blockjobs: add explicit job management |
Date: |
Mon, 12 Mar 2018 17:23:19 +0100 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
Am 10.03.2018 um 09:27 hat John Snow geschrieben:
> This series seeks to address two distinct but closely related issues
> concerning the job management API.
>
> (1) For jobs that complete when a monitor is not attached and receiving
> events or notifications, there's no way to discern the job's final
> return code. Jobs must remain in the query list until dismissed
> for reliable management.
>
> (2) Jobs that change the block graph structure at an indeterminate point
> after the job starts compete with the management layer that relies
> on that graph structure to issue meaningful commands.
>
> This structure should change only at the behest of the management
> API, and not asynchronously at unknown points in time. Before a job
> issues such changes, it must rely on explicit and synchronous
> confirmation from the management API.
>
> These changes are implemented by formalizing a State Transition Machine
> for the BlockJob subsystem.
Thanks, applied to the block branch.
Kevin
- [Qemu-devel] [PATCH v5 21/21] tests/test-blockjob: test cancellations, (continued)
[Qemu-devel] [PATCH v5 11/21] blockjobs: add block_job_dismiss, John Snow, 2018/03/10
[Qemu-devel] [PATCH v5 17/21] blockjobs: add PENDING status and event, John Snow, 2018/03/10
[Qemu-devel] [PATCH v5 19/21] blockjobs: Expose manual property, John Snow, 2018/03/10
Re: [Qemu-devel] [PATCH v5 00/21] blockjobs: add explicit job management,
Kevin Wolf <=
Re: [Qemu-devel] [PATCH v5 00/21] blockjobs: add explicit job management, no-reply, 2018/03/12