From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, armbru@redhat.com,
qemu-devel@nongnu.org, andrey.shinkevich@virtuozzo.com,
den@openvz.org, mreitz@redhat.com, jsnow@redhat.com,
dgilbert@redhat.com
Subject: [PATCH 0/7] Apply COR-filter to the block-stream permanently
Date: Mon, 20 Apr 2020 21:36:39 +0300 [thread overview]
Message-ID: <1587407806-109784-1-git-send-email-andrey.shinkevich@virtuozzo.com> (raw)
Note: this series is based on the one "block: Deal with filters"
by Max Reitz that can be found in the branches:
https://git.xanclic.moe/XanClic/qemu child-access-functions-v6
https://github.com/XanClic/qemu child-access-functions-v6
When running iotests, apply "char-socket: Fix race condition"
to avoid sporadic segmentation faults.
With this series, all the block-stream COR operations pass through
the COR-filter.
Andrey Shinkevich (7):
block: prepare block-stream for using COR-filter
stream: exclude a link to filter from freezing
block: protect parallel jobs from overlapping
copy-on-read: Support refreshing filename
qapi: add filter-node-name to block-stream
iotests: prepare 245 for using filter in block-stream
block: apply COR-filter to block-stream jobs
block/copy-on-read.c | 7 ++
block/stream.c | 170 +++++++++++++++++++++++++++++++++++++++------
blockdev.c | 15 +++-
blockjob.c | 15 +++-
include/block/block_int.h | 7 +-
monitor/hmp-cmds.c | 4 +-
qapi/block-core.json | 6 ++
tests/qemu-iotests/030 | 6 +-
tests/qemu-iotests/141.out | 2 +-
tests/qemu-iotests/245 | 15 ++--
10 files changed, 210 insertions(+), 37 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-04-20 18:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 18:36 Andrey Shinkevich [this message]
2020-04-20 18:36 ` [PATCH 1/7] block: prepare block-stream for using COR-filter Andrey Shinkevich
2020-04-21 12:23 ` Vladimir Sementsov-Ogievskiy
2020-04-20 18:36 ` [PATCH 2/7] stream: exclude a link to filter from freezing Andrey Shinkevich
2020-04-21 12:27 ` Vladimir Sementsov-Ogievskiy
2020-04-20 18:36 ` [PATCH 3/7] block: protect parallel jobs from overlapping Andrey Shinkevich
2020-04-21 12:33 ` Vladimir Sementsov-Ogievskiy
2020-04-20 18:36 ` [PATCH 4/7] copy-on-read: Support refreshing filename Andrey Shinkevich
2020-04-21 12:36 ` Vladimir Sementsov-Ogievskiy
2020-04-20 18:36 ` [PATCH 5/7] qapi: add filter-node-name to block-stream Andrey Shinkevich
2020-04-20 18:43 ` Eric Blake
2020-04-21 12:05 ` Dr. David Alan Gilbert
2020-04-21 12:40 ` Vladimir Sementsov-Ogievskiy
2020-04-21 12:45 ` Vladimir Sementsov-Ogievskiy
2020-04-20 18:36 ` [PATCH 6/7] iotests: prepare 245 for using filter in block-stream Andrey Shinkevich
2020-04-20 18:36 ` [PATCH 7/7] block: apply COR-filter to block-stream jobs Andrey Shinkevich
2020-04-21 12:58 ` Vladimir Sementsov-Ogievskiy
2020-04-27 4:08 ` Andrey Shinkevich
2020-04-27 6:44 ` Vladimir Sementsov-Ogievskiy
2020-04-21 13:12 ` [PATCH 0/7] Apply COR-filter to the block-stream permanently Vladimir Sementsov-Ogievskiy
2020-04-27 4:13 ` Andrey Shinkevich
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=1587407806-109784-1-git-send-email-andrey.shinkevich@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).