Re: [PATCH 0/2] iotests: More _filter_img_create fixes

2020-07-12 Thread Max Reitz
On 10.07.20 19:18, John Snow wrote: > > > On 7/10/20 12:32 PM, Max Reitz wrote: >> Hi, >> >> I’m sorry. >> >> John, could I ask you to test whether this series fixes the problems >> you’re seeing? >> > > This is based on kwolf/block, I see. > > By the time you return to reading work email, this

Re: [PATCH v8 03/10] qcow2_format.py: change Qcow2BitmapExt initialization method

2020-07-12 Thread Andrey Shinkevich
On 11.07.2020 19:34, Vladimir Sementsov-Ogievskiy wrote: 03.07.2020 16:13, Andrey Shinkevich wrote: There are two ways to initialize a class derived from Qcow2Struct: 1. Pass a block of binary data to the constructor. 2. Pass the file descriptor to allow reading the file from constructor. Let's

Re: [PATCH v3 3/4] hw/block/nvme: Fix pmrmsc register size

2020-07-12 Thread Dmitry Fomichev
On Tue, 2020-06-30 at 13:04 +0200, Philippe Mathieu-Daudé wrote: > The Persistent Memory Region Controller Memory Space Control > register is 64-bit wide. See 'Figure 68: Register Definition' > of the 'NVM Express Base Specification Revision 1.4'. > > Fixes: 6cf9413229 ("introduce PMR support from

Re: [PATCH v3 4/4] hw/block/nvme: Align I/O BAR to 4 KiB

2020-07-12 Thread Dmitry Fomichev
On Tue, 2020-06-30 at 13:04 +0200, Philippe Mathieu-Daudé wrote: > Simplify the NVMe emulated device by aligning the I/O BAR to 4 KiB. > > Reviewed-by: Klaus Jensen > Signed-off-by: Philippe Mathieu-Daudé > --- > include/block/nvme.h | 2 ++ > hw/block/nvme.c | 5 ++--- > 2 files changed,

Re: [PATCH v3 2/4] hw/block/nvme: Use QEMU_PACKED on hardware/packet structures

2020-07-12 Thread Dmitry Fomichev
On Tue, 2020-06-30 at 13:04 +0200, Philippe Mathieu-Daudé wrote: > These structures either describe hardware registers, or > commands ('packets') to send to the hardware. To forbid > the compiler to optimize and change fields alignment, > mark the structures as packed. > > Reviewed-by: Klaus Jens

Re: [PATCH 1/2] tests/acceptance/boot_linux: Truncate SD card image to power of 2

2020-07-12 Thread Niek Linnenbank
On Tue, Jul 7, 2020 at 3:21 PM Philippe Mathieu-Daudé wrote: > In the next commit we won't allow SD card images with invalid > size (not aligned to a power of 2). Prepare the tests: add the > pow2ceil() and image_pow2ceil_truncate() methods and truncate > the images of the tests using SD cards. >

[PATCH v4 1/3] scripts/simplebench: compare write request performance

2020-07-12 Thread Andrey Shinkevich
The script 'bench_write_req.py' allows comparing performances of write request for two qemu-img binary files. An example with (qemu-img binary 1) and without (qemu-img binary 2) the applied patch "qcow2: skip writing zero buffers to empty COW areas" (git commit ID: c8bb23cbdbe32f5) has the followin

[PATCH v4 2/3] scripts/simplebench: allow writing to non-empty image

2020-07-12 Thread Andrey Shinkevich
Add 'empty_image' parameter to the function bench_write_req() and to the test cases that will allow writing to the non-empty clusters of the image if the 'empty_image' parameter set to False. Signed-off-by: Andrey Shinkevich --- scripts/simplebench/bench_write_req.py | 27 +--

[PATCH v4 0/3] scripts/simplebench: add bench_write_req.py test

2020-07-12 Thread Andrey Shinkevich
The script 'bench_write_req.py' allows comparing performances of write request for two qemu-img binary files. If you made a change in QEMU code and want to check the write requests performance, you will want to build two qemu-img binary files with and without your change. Then you specify paths

[PATCH v4 3/3] scripts/simplebench: add unaligned data case to bench_write_req

2020-07-12 Thread Andrey Shinkevich
Add a test case with writhing data unaligned to the image clusters. This case does not involve the COW optimization introduced with the patch "qcow2: skip writing zero buffers to empty COW areas" (git commit ID: c8bb23cbdbe32f5). Signed-off-by: Andrey Shinkevich --- scripts/simplebench/bench_wri

[PATCH v3 1/3] scripts/simplebench: compare write request performance

2020-07-12 Thread Andrey Shinkevich
The script 'bench_write_req.py' allows comparing performances of write request for two qemu-img binary files. An example with (qemu-img binary 1) and without (qemu-img binary 2) the applied patch "qcow2: skip writing zero buffers to empty COW areas" (git commit ID: c8bb23cbdbe32f5) has the followin

[PATCH v3 0/3] scripts/simplebench: add bench_write_req.py test

2020-07-12 Thread Andrey Shinkevich
The script 'bench_write_req.py' allows comparing performances of write request for two qemu-img binary files. If you made a change in QEMU code and want to check the write requests performance, you will want to build two qemu-img binary files with and without your change. Then you specify paths

[PATCH v3 2/3] scripts/simplebench: allow writing to non-empty image

2020-07-12 Thread Andrey Shinkevich
Add 'empty_image' parameter to the function bench_write_req() and to the test cases that will allow writing to the non-empty clusters of the image if the 'empty_image' parameter set to False. Signed-off-by: Andrey Shinkevich --- scripts/simplebench/bench_write_req.py | 27 +--

[PATCH v3 3/3] scripts/simplebench: add unaligned data case to bench_write_req

2020-07-12 Thread Andrey Shinkevich
Add a test case with writhing data unaligned to the image clusters. This case does not involve the COW optimization introduced with the patch "qcow2: skip writing zero buffers to empty COW areas" (git commit ID: c8bb23cbdbe32f5). Signed-off-by: Andrey Shinkevich --- scripts/simplebench/bench_wri

Re: [PATCH v2] scripts/simplebench: compare write request performance

2020-07-12 Thread Andrey Shinkevich
On 11.07.2020 16:05, Vladimir Sementsov-Ogievskiy wrote: 26.06.2020 17:31, Andrey Shinkevich wrote: The script 'bench_write_req.py' allows comparing performances of write request for two qemu-img binary files. An example with (qemu-img binary 1) and without (qemu-img binary 2) the applied patch

Re: [PATCH] block/amend: Check whether the node exists

2020-07-12 Thread Maxim Levitsky
On Fri, 2020-07-10 at 11:50 +0200, Max Reitz wrote: > We should check whether the user-specified node-name actually refers to > a node. The simplest way to do that is to use bdrv_lookup_bs() instead > of bdrv_find_node() (the former wraps the latter, and produces an error > message if necessary).