From: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH V12 0/6] add-cow file format
Date: Fri, 10 Aug 2012 23:39:39 +0800 [thread overview]
Message-ID: <1344613185-12308-1-git-send-email-wdongxu@linux.vnet.ibm.com> (raw)
This will introduce a new file format: add-cow.
add-cow can benefit from other available functions, such as path_has_protocol and
qed_read_string, so we will make them public.
Now add-cow is still using QEMUOptionParameter, not QemuOpts, I will send a
separate patch series to convert.
snapshot_blkdev are not supported now for add-cow, after converting QEMUOptionParameter
to QemuOpts, will add related code.
v11->v12:
1) Removed un-used feature bit.
2) Share cache code with qcow2.c.
3) Remove snapshot_blkdev support, will add it in another patch.
5) COW Bitmap field in add-cow file will be multiple of 65536.
6) fix grammer and typo.
Dong Xu Wang (6):
docs: document for add cow file format
make path_has_protocol non-static
qed_read_string to bdrv_read_string
rename qcow2-cache.c to block-cache.c
add-cow file format
qemu-iotests
block.c | 29 ++-
block.h | 6 +
block/Makefile.objs | 4 +-
block/add-cow.c | 613 ++++++++++++++++++++++++++++++++++++++++++
block/add-cow.h | 85 ++++++
block/qcow2-cache.c | 323 ----------------------
block/qcow2-cluster.c | 66 +++--
block/qcow2-refcount.c | 66 +++--
block/qcow2.c | 36 ++--
block/qcow2.h | 24 +--
block/qed.c | 29 +--
block_int.h | 2 +
docs/specs/add-cow.txt | 123 +++++++++
tests/qemu-iotests/017 | 2 +-
tests/qemu-iotests/020 | 2 +-
tests/qemu-iotests/check | 4 +-
tests/qemu-iotests/common | 6 +
tests/qemu-iotests/common.rc | 19 ++
trace-events | 13 +-
19 files changed, 994 insertions(+), 458 deletions(-)
create mode 100644 block/add-cow.c
create mode 100644 block/add-cow.h
delete mode 100644 block/qcow2-cache.c
create mode 100644 docs/specs/add-cow.txt
next reply other threads:[~2012-08-10 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 15:39 Dong Xu Wang [this message]
2012-08-10 15:39 ` [Qemu-devel] [PATCH V12 1/6] docs: document for add-cow file format Dong Xu Wang
2012-09-06 17:27 ` Michael Roth
2012-09-10 1:48 ` Dong Xu Wang
2012-09-10 15:23 ` Kevin Wolf
2012-09-11 2:12 ` Dong Xu Wang
2012-08-10 15:39 ` [Qemu-devel] [PATCH V12 2/6] make path_has_protocol non-static Dong Xu Wang
2012-09-06 17:27 ` Michael Roth
2012-08-10 15:39 ` [Qemu-devel] [PATCH V12 3/6] qed_read_string to bdrv_read_string Dong Xu Wang
2012-09-06 17:32 ` Michael Roth
2012-09-10 1:49 ` Dong Xu Wang
2012-08-10 15:39 ` [Qemu-devel] [PATCH V12 4/6] rename qcow2-cache.c to block-cache.c Dong Xu Wang
2012-09-06 17:52 ` Michael Roth
2012-09-10 2:14 ` Dong Xu Wang
2012-09-11 8:41 ` Kevin Wolf
2012-08-10 15:39 ` [Qemu-devel] [PATCH V12 5/6] add-cow file format Dong Xu Wang
2012-09-06 20:19 ` Michael Roth
2012-09-10 2:25 ` Dong Xu Wang
2012-09-11 9:44 ` Kevin Wolf
2012-09-11 9:40 ` Kevin Wolf
2012-09-12 7:28 ` Dong Xu Wang
2012-09-12 7:50 ` Kevin Wolf
2012-08-10 15:39 ` [Qemu-devel] [PATCH V12 6/6] add-cow: add qemu-iotests support Dong Xu Wang
2012-09-11 9:55 ` Kevin Wolf
2012-08-23 5:34 ` [Qemu-devel] [PATCH V12 0/6] add-cow file format Dong Xu Wang
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=1344613185-12308-1-git-send-email-wdongxu@linux.vnet.ibm.com \
--to=wdongxu@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--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).