All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Eric Blake <eblake@redhat.com>, Sam Li <faithilikerun@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <fam@euphon.net>,
	Jeuk Kim <jeuk20.kim@samsung.com>,
	Daejun Park <daejun7.park@samsung.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v17 0/9] Add full zoned storage emulation to the qcow2 driver
Date: Fri, 20 Nov 2026 15:58:26 +0100	[thread overview]
Message-ID: <awBgEvaATwrbgIc6@ryzen> (raw)
In-Reply-To: <20261112114918.1269168-1-cassel@kernel.org>

On Thu, Nov 12, 2026 at 12:49:09PM +0100, Niklas Cassel wrote:
> This patch series adds a new extension - zoned format - to the
> qcow2 driver, allowing full zoned storage emulation on a qcow2
> image file. A user can attach such an image to a guest and have
> it appear as a host-managed zoned block device.
> 
> The zoned format is opt-in through a new qcow2 header extension
> that pins the zone geometry. Behind the extension is a dedicated
> zoned metadata region that stores one 8-byte write pointer (WP)
> per zone. The extension is gated by an incompatible bit, so an
> older qcow2 implementation cannot accidentally open the image.

[...]


Hi Kevin, Hanna, Stefan,


It would be great to get some guidance on what is needed to get this
series accepted. It is now at v17. Is there anything I can do to help
get it merged?

Almost all of the new code is only used by images created with the new
zoned feature, so the risk for existing users should be very low.

The only changes in code that every qcow2 image goes through are:

- Writes now go through qcow2_co_pwv_part(), but outside the zoned
  branches the code is the same as the old qcow2_co_pwritev_part().

- The additions to qcow2_refresh_limits(), qcow2_inactivate() and
  qcow2_do_close() only have an effect when the image has zoned
  metadata.

- qcow2_cache_set_dependency() now returns early when the dependency is
  already set, which avoids a redundant flush, without changing the
  write ordering. I could move this to a separate patch if you prefer.

Apart from one more entry in the feature name table of newly written
images, images that don't use the new zoned feature are unaffected.


Thanks,
Niklas


      parent reply	other threads:[~2026-11-20 14:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 11:49 [PATCH v17 0/9] Add full zoned storage emulation to the qcow2 driver Niklas Cassel
2026-11-12 11:49 ` [PATCH v17 1/9] docs/qcow2: add the zoned format feature Niklas Cassel
2026-11-12 11:49 ` [PATCH v17 2/9] qcow2: add configurations for zoned format extension Niklas Cassel
2026-11-12 11:49 ` [PATCH v17 3/9] block: define errnos for zone protocol errors Niklas Cassel
2026-11-15 23:45   ` Damien Le Moal
2026-11-12 11:49 ` [PATCH v17 4/9] qcow2: add zoned emulation capability Niklas Cassel
2026-11-12 11:49 ` [PATCH v17 5/9] iotests: test the zoned format feature for qcow2 file Niklas Cassel
2026-11-12 11:49 ` [PATCH v17 6/9] qcow2: validate the write pointer table when opening an image Niklas Cassel
2026-11-12 11:49 ` [PATCH v17 7/9] virtio-blk: report zone errors with their zone status codes Niklas Cassel
2026-11-15 23:48   ` Damien Le Moal
2026-11-12 11:49 ` [PATCH v17 8/9] block: add accessors for the zone model, capacity and open zone limit Niklas Cassel
2026-11-15 23:48   ` Damien Le Moal
2026-11-12 11:49 ` [PATCH v17 9/9] scsi: add the sense codes of zoned block devices Niklas Cassel
2026-11-15 23:49   ` Damien Le Moal
2026-11-20 14:58 ` Niklas Cassel [this message]

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=awBgEvaATwrbgIc6@ryzen \
    --to=cassel@kernel.org \
    --cc=armbru@redhat.com \
    --cc=daejun7.park@samsung.com \
    --cc=dlemoal@kernel.org \
    --cc=eblake@redhat.com \
    --cc=faithilikerun@gmail.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=jeuk20.kim@samsung.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pierrick.bouvier@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.