From: Sam Li <faithilikerun@gmail.com>
To: qemu-devel@nongnu.org
Cc: damien.lemoal@opensource.wdc.com, Kevin Wolf <kwolf@redhat.com>,
hare@suse.de, Hanna Reitz <hreitz@redhat.com>,
Markus Armbruster <armbru@redhat.com>, Fam Zheng <fam@euphon.net>,
stefanha@redhat.com, Eric Blake <eblake@redhat.com>,
qemu-block@nongnu.org, dmitry.fomichev@wdc.com,
Sam Li <faithilikerun@gmail.com>
Subject: [PATCH v10 4/7] raw-format: add zone operations to pass through requests
Date: Thu, 29 Sep 2022 16:36:28 +0800 [thread overview]
Message-ID: <20220929083631.61899-5-faithilikerun@gmail.com> (raw)
In-Reply-To: <20220929083631.61899-1-faithilikerun@gmail.com>
raw-format driver usually sits on top of file-posix driver. It needs to
pass through requests of zone commands.
Signed-off-by: Sam Li <faithilikerun@gmail.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
---
block/raw-format.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/block/raw-format.c b/block/raw-format.c
index 69fd650eaf..6b20bd22ef 100644
--- a/block/raw-format.c
+++ b/block/raw-format.c
@@ -314,6 +314,17 @@ static int coroutine_fn raw_co_pdiscard(BlockDriverState *bs,
return bdrv_co_pdiscard(bs->file, offset, bytes);
}
+static int coroutine_fn raw_co_zone_report(BlockDriverState *bs, int64_t offset,
+ unsigned int *nr_zones,
+ BlockZoneDescriptor *zones) {
+ return bdrv_co_zone_report(bs->file->bs, offset, nr_zones, zones);
+}
+
+static int coroutine_fn raw_co_zone_mgmt(BlockDriverState *bs, BlockZoneOp op,
+ int64_t offset, int64_t len) {
+ return bdrv_co_zone_mgmt(bs->file->bs, op, offset, len);
+}
+
static int64_t raw_getlength(BlockDriverState *bs)
{
int64_t len;
@@ -614,6 +625,8 @@ BlockDriver bdrv_raw = {
.bdrv_co_pwritev = &raw_co_pwritev,
.bdrv_co_pwrite_zeroes = &raw_co_pwrite_zeroes,
.bdrv_co_pdiscard = &raw_co_pdiscard,
+ .bdrv_co_zone_report = &raw_co_zone_report,
+ .bdrv_co_zone_mgmt = &raw_co_zone_mgmt,
.bdrv_co_block_status = &raw_co_block_status,
.bdrv_co_copy_range_from = &raw_co_copy_range_from,
.bdrv_co_copy_range_to = &raw_co_copy_range_to,
--
2.37.3
next prev parent reply other threads:[~2022-09-29 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 8:36 [PATCH v10 0/7] Add support for zoned device Sam Li
2022-09-29 8:36 ` [PATCH v10 1/7] include: add zoned device structs Sam Li
2022-09-29 8:36 ` [PATCH v10 2/7] file-posix: introduce helper functions for sysfs attributes Sam Li
2022-09-29 8:36 ` [PATCH v10 3/7] block: add block layer APIs resembling Linux ZonedBlockDevice ioctls Sam Li
2022-10-03 17:47 ` Stefan Hajnoczi
2022-10-03 23:23 ` Damien Le Moal
2022-10-06 15:17 ` Stefan Hajnoczi
2022-10-06 23:03 ` Damien Le Moal
2022-10-08 3:42 ` Sam Li
2022-10-08 2:02 ` Sam Li
2022-09-29 8:36 ` Sam Li [this message]
2022-09-29 8:36 ` [PATCH v10 5/7] config: add check to block layer Sam Li
2022-09-29 8:36 ` [PATCH v10 6/7] qemu-iotests: test new zone operations Sam Li
2022-09-29 8:36 ` [PATCH v10 7/7] docs/zoned-storage: add zoned device documentation Sam Li
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=20220929083631.61899-5-faithilikerun@gmail.com \
--to=faithilikerun@gmail.com \
--cc=armbru@redhat.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=hare@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).