Re: [PATCH v3 2/3] block: introduce zone append write for zoned devices

On 10/10/22 11:33, Sam Li wrote: > A zone append command is a write operation that specifies the first > logical block of a zone as the write position. When writing to a zoned > block device using zone append, the byte offset of writes is pointing > to the write pointer of that zone. Upon

Re: [PATCH v11 3/7] block: add block layer APIs resembling Linux ZonedBlockDevice ioctls

Damien Le Moal 于2022年10月13日周四 13:45写道： > > On 10/13/22 14:33, Sam Li wrote: > > Damien Le Moal 于2022年10月13日周四 12:41写道： > >> > >> On 10/10/22 11:21, Sam Li wrote: > >>> Add a new zoned_host_device BlockDriver. The zoned_host_device option > >>> accepts only zoned host block devices. By adding

Re: [PATCH v11 3/7] block: add block layer APIs resembling Linux ZonedBlockDevice ioctls

On 10/13/22 14:33, Sam Li wrote: > Damien Le Moal 于2022年10月13日周四 12:41写道： >> >> On 10/10/22 11:21, Sam Li wrote: >>> Add a new zoned_host_device BlockDriver. The zoned_host_device option >>> accepts only zoned host block devices. By adding zone management >>> operations in this new BlockDriver,

Re: [PATCH v2] pci: Assert that capabilities never overlap

On Thu, Sep 29, 2022 at 7:55 PM Markus Armbruster wrote: > > Akihiko Odaki writes: > > > On Mon, Sep 5, 2022 at 6:26 PM Markus Armbruster wrote: > >> > >> Akihiko Odaki writes: > >> > >> > On Fri, Sep 2, 2022 at 7:23 PM Markus Armbruster > >> > wrote: > >> >> > >> >> Akihiko Odaki writes: >

Re: [PATCH v11 3/7] block: add block layer APIs resembling Linux ZonedBlockDevice ioctls

Damien Le Moal 于2022年10月13日周四 12:41写道： > > On 10/10/22 11:21, Sam Li wrote: > > Add a new zoned_host_device BlockDriver. The zoned_host_device option > > accepts only zoned host block devices. By adding zone management > > operations in this new BlockDriver, users can use the new block > > layer

Re: [PATCH v3 1/3] file-posix:add the tracking of the zones write pointers

On 10/10/22 11:33, Sam Li wrote: > Since Linux doesn't have a user API to issue zone append operations to > zoned devices from user space, the file-posix driver is modified to add > zone append emulation using regular writes. To do this, the file-posix > driver tracks the wp location of all zones

Re: [PATCH v11 7/7] docs/zoned-storage: add zoned device documentation

On 10/10/22 11:21, Sam Li wrote: > Add the documentation about the zoned device support to virtio-blk > emulation. > > Signed-off-by: Sam Li > Reviewed-by: Stefan Hajnoczi > --- > docs/devel/zoned-storage.rst | 40 ++ > docs/system/qemu-block-drivers.rst.inc |

Re: [PATCH v11 3/7] block: add block layer APIs resembling Linux ZonedBlockDevice ioctls

On 10/10/22 11:21, Sam Li wrote: > Add a new zoned_host_device BlockDriver. The zoned_host_device option > accepts only zoned host block devices. By adding zone management > operations in this new BlockDriver, users can use the new block > layer APIs including Report Zone and four zone management

Re: [PULL 00/50] Block layer patches

Applied, thanks. Please update the changelog at https://wiki.qemu.org/ChangeLog/7.2 for any user-visible changes. signature.asc Description: PGP signature

Re: [PATCH v7 for-7.2 00/15] block: cleanup backing and file handling

ping On 9/19/22 20:20, Vladimir Sementsov-Ogievskiy wrote: ping. Seems, all patches are reviewed On 7/26/22 23:11, Vladimir Sementsov-Ogievskiy wrote: Hi all! That's the first part of "[PATCH v5 00/45] Transactional block-graph modifying API", updated and is fully reviewed by Hanna. v7: add

Re: [PATCH v2 00/11] iotests: use vm.cmd()

ping On 9/19/22 20:16, Vladimir Sementsov-Ogievskiy wrote: ping On 6/6/22 10:27, Vladimir Sementsov-Ogievskiy wrote: Hi all! Let's get rid of pattern result = self.vm.qmp(...) self.assert_qmp(result, 'return', {}) And switch to just self.vm.cmd(...) Supersedes:

Re: [PATCH] tests/unit/test-image-locking: Fix handling of temporary files

On Wed, Oct 12, 2022 at 4:59 PM Thomas Huth wrote: > > test-image-locking leaves some temporary files around - clean > them up. While we're at it, test-image-locking is a unit test, > so it should not use "qtest.*" for temporary file names. Give > them better names instead, so that it clear where

Re: [PATCH] tests/unit/test-image-locking: Fix handling of temporary files

On 12/10/2022 11.21, Marc-André Lureau wrote: Hi On Wed, Oct 12, 2022 at 1:03 PM Thomas Huth > wrote: test-image-locking leaves some temporary files around - clean them up. While we're at it, test-image-locking is a unit test, so it should not use

Re: [PATCH] tests/unit/test-image-locking: Fix handling of temporary files

Hi On Wed, Oct 12, 2022 at 1:03 PM Thomas Huth wrote: > test-image-locking leaves some temporary files around - clean > them up. While we're at it, test-image-locking is a unit test, > so it should not use "qtest.*" for temporary file names. Give > them better names instead, so that it clear

[PATCH] tests/unit/test-image-locking: Fix handling of temporary files

test-image-locking leaves some temporary files around - clean them up. While we're at it, test-image-locking is a unit test, so it should not use "qtest.*" for temporary file names. Give them better names instead, so that it clear where the temporary files come from. Signed-off-by: Thomas Huth

Re: [PATCH] hw/block/nvme: re-enable NVMe PCI hotplug

On Okt 12 08:24, Hannes Reinecke wrote: > On 10/10/22 19:01, Daniel Wagner wrote: > > On Tue, May 11, 2021 at 06:12:47PM +0200, Hannes Reinecke wrote: > > > On 5/11/21 6:03 PM, Klaus Jensen wrote: > > > > On May 11 16:54, Hannes Reinecke wrote: > > > > > On 5/11/21 3:37 PM, Klaus Jensen wrote: > >

Re: [PATCH 2/2] tests/qtest/ide-test: Verify READ NATIVE MAX ADDRESS is not limited

On 10/10/2022 10.52, Lev Kujawski wrote: Verify that the ATA command READ NATIVE MAX ADDRESS returns the last valid CHS tuple for the native device rather than any limit established by INITIALIZE DEVICE PARAMETERS. Signed-off-by: Lev Kujawski --- tests/qtest/ide-test.c | 47

Re: [PATCH] hw/block/nvme: re-enable NVMe PCI hotplug

On 10/10/22 19:01, Daniel Wagner wrote: On Tue, May 11, 2021 at 06:12:47PM +0200, Hannes Reinecke wrote: On 5/11/21 6:03 PM, Klaus Jensen wrote: On May 11 16:54, Hannes Reinecke wrote: On 5/11/21 3:37 PM, Klaus Jensen wrote: On May 11 15:12, Hannes Reinecke wrote: On 5/11/21 2:22 PM, Klaus