From: development@manuel-bentele.de
To: linux-block@vger.kernel.org
Cc: Manuel Bentele <development@manuel-bentele.de>
Subject: [PATCH 5/5] doc: admin-guide: add QCOW2 file format to loop device documentation
Date: Sat, 24 Aug 2019 00:56:19 +0200 [thread overview]
Message-ID: <20190823225619.15530-6-development@manuel-bentele.de> (raw)
In-Reply-To: <20190823225619.15530-1-development@manuel-bentele.de>
From: Manuel Bentele <development@manuel-bentele.de>
The existing documentation about the loop block device is extended by
a section about the QCOW2 file format driver. The documentation is written
in the reST kernel documentation format.
Signed-off-by: Manuel Bentele <development@manuel-bentele.de>
---
Documentation/admin-guide/blockdev/loop.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/admin-guide/blockdev/loop.rst b/Documentation/admin-guide/blockdev/loop.rst
index 69d8172c85db..3a5897a14c8b 100644
--- a/Documentation/admin-guide/blockdev/loop.rst
+++ b/Documentation/admin-guide/blockdev/loop.rst
@@ -72,3 +72,14 @@ image file. It supports discarding, asynchrounous IO, flushing and cryptoloop
support.
The driver's kernel module is named *loop_file_fmt_raw*.
+
+
+QCOW
+~~~~
+
+The QCOW file format driver implements QEMU's copy on write file format in
+version 2. At the moment, the file format driver only supports the reading
+of QCOW2 disk image files. It does not support writing to QCOW2 images, the
+recovery of broken QCOW images, snapshots and reference counts.
+
+The driver's kernel module is named *loop_file_fmt_qcow*.
--
2.23.0
next prev parent reply other threads:[~2019-08-23 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 22:56 [PATCH 0/5] block: loop: add file format subsystem and QCOW2 file format driver development
2019-08-23 22:56 ` [PATCH 2/5] doc: admin-guide: add loop block device documentation development
2019-08-23 22:56 ` [PATCH 3/5] doc: driver-api: add loop file format subsystem API documentation development
2019-08-23 22:56 ` [PATCH 4/5] block: loop: add QCOW2 loop file format driver (read-only) development
2019-08-23 22:56 ` development [this message]
2019-08-24 3:37 ` [PATCH 0/5] block: loop: add file format subsystem and QCOW2 file format driver Bart Van Assche
2019-08-24 9:14 ` Manuel Bentele
2019-08-24 16:04 ` Bart Van Assche
2019-08-25 12:15 ` Manuel Bentele
2019-09-09 22:12 ` Manuel Bentele
2019-08-24 11:10 ` Manuel Bentele
2019-09-12 2:24 ` Ming Lei
2019-09-13 11:57 ` Manuel Bentele
2019-09-16 2:11 ` Ming Lei
2019-09-18 10:26 ` Simon Rettberg
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=20190823225619.15530-6-development@manuel-bentele.de \
--to=development@manuel-bentele.de \
--cc=linux-block@vger.kernel.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).