From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, pkrempa@redhat.com, jtc@redhat.com,
qemu-devel@nongnu.org, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] blockjobs: add explicit job culling
Date: Mon, 2 Oct 2017 23:15:53 -0400 [thread overview]
Message-ID: <20171003031556.15173-1-jsnow@redhat.com> (raw)
For jobs that complete when a monitor isn't looking, there's no way to
tell what the job's final return code was. We need to allow jobs to
remain in the list until queried for reliable management.
This is an RFC; tests are on the way.
(Tested only manually via qmp-shell for now.)
John Snow (3):
blockjob: add manual-cull property
qmp: add block-job-cull command
blockjob: expose manual-cull property
block/backup.c | 20 +++++++++---------
block/commit.c | 2 +-
block/mirror.c | 2 +-
block/replication.c | 5 +++--
block/stream.c | 2 +-
block/trace-events | 1 +
blockdev.c | 28 +++++++++++++++++++++----
blockjob.c | 46 +++++++++++++++++++++++++++++++++++++++--
include/block/block_int.h | 8 +++++---
include/block/blockjob.h | 21 +++++++++++++++++++
include/block/blockjob_int.h | 2 +-
qapi/block-core.json | 49 ++++++++++++++++++++++++++++++++++++--------
tests/test-blockjob-txn.c | 2 +-
tests/test-blockjob.c | 2 +-
14 files changed, 155 insertions(+), 35 deletions(-)
--
2.9.5
next reply other threads:[~2017-10-03 3:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 3:15 John Snow [this message]
2017-10-03 3:15 ` [Qemu-devel] [PATCH 1/3] blockjob: add manual-cull property John Snow
2017-10-03 3:15 ` [Qemu-devel] [PATCH 2/3] qmp: add block-job-cull command John Snow
2017-10-03 3:15 ` [Qemu-devel] [PATCH 3/3] blockjob: expose manual-cull property John Snow
2017-10-03 15:57 ` Paolo Bonzini
2017-10-03 15:59 ` John Snow
2017-10-03 17:43 ` Jeff Cody
2017-10-04 1:32 ` John Snow
2017-10-03 9:20 ` [Qemu-devel] [PATCH 0/3] blockjobs: add explicit job culling Vladimir Sementsov-Ogievskiy
2017-10-03 14:42 ` John Snow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171003031556.15173-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=jtc@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).