From: Roman Kagan <rvkagan@yandex-team.ru>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Keith Busch" <kbusch@kernel.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH v5 0/5] block: widen and check consistency of size-related BlockConf properties
Date: Tue, 26 May 2020 14:00:52 +0300 [thread overview]
Message-ID: <20200526110052.GA6355@rvkaganb.lan> (raw)
In-Reply-To: <20200526081740.256236-1-rvkagan@yandex-team.ru>
Please ignore the series, I forgot xen-block device.
Roman.
On Tue, May 26, 2020 at 11:17:35AM +0300, Roman Kagan wrote:
> BlockConf includes several properties counted in bytes.
>
> Enhance their handling in a some aspects, specifically
>
> - accept common size suffixes (k, m)
> - perform consistency checks on the values, to prevent their silent
> truncation and rounding
> - lift the upper limit on physical_block_size and logical_block_size
>
> Also fix the accessor for opt_io_size in virtio-blk to make it match the size
> of the field.
>
> History:
> v4 -> v5:
> - re-split the patches [Philippe]
> - fix/reword error messages [Philippe, Kevin]
> - do early return on failed consistency check [Philippe]
> - use QEMU_IS_ALIGNED instead of open coding [Philippe]
> - make all BlockConf size props support suffixes
> - expand the log for virtio-blk opt_io_size [Michael]
>
> v3 -> v4:
> - add patch to fix opt_io_size width in virtio-blk
> - add patch to perform consistency checks [Kevin]
> - check min_io_size against truncation [Kevin]
>
> v2 -> v3:
> - mention qcow2 cluster size limit in the log and comment [Eric]
>
> v1 -> v2:
> - cap the property at 2 MiB [Eric]
> - accept size suffixes
>
> Roman Kagan (5):
> virtio-blk: store opt_io_size with correct size
> block: consolidate blocksize properties consistency checks
> qdev-properties: blocksize: use same limits in code and description
> block: make size-related BlockConf properties accept size suffixes
> block: lift blocksize property limit to 2 MiB
>
> include/hw/block/block.h | 18 +-
> include/hw/qdev-properties.h | 2 +-
> hw/block/block.c | 64 ++++-
> hw/block/fdc.c | 5 +-
> hw/block/nvme.c | 5 +-
> hw/block/virtio-blk.c | 9 +-
> hw/core/qdev-properties.c | 109 +++----
> hw/ide/qdev.c | 5 +-
> hw/scsi/scsi-disk.c | 12 +-
> hw/usb/dev-storage.c | 5 +-
> tests/qemu-iotests/172.out | 532 +++++++++++++++++------------------
> 11 files changed, 423 insertions(+), 343 deletions(-)
>
> --
> 2.26.2
>
>
prev parent reply other threads:[~2020-05-26 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 8:17 [PATCH v5 0/5] block: widen and check consistency of size-related BlockConf properties Roman Kagan
2020-05-26 8:17 ` [PATCH v5 1/5] virtio-blk: store opt_io_size with correct size Roman Kagan
2020-05-26 8:17 ` [PATCH v5 2/5] block: consolidate blocksize properties consistency checks Roman Kagan
2020-05-26 8:17 ` [PATCH v5 3/5] qdev-properties: blocksize: use same limits in code and description Roman Kagan
2020-05-26 8:17 ` [PATCH v5 4/5] block: make size-related BlockConf properties accept size suffixes Roman Kagan
2020-05-26 8:17 ` [PATCH v5 5/5] block: lift blocksize property limit to 2 MiB Roman Kagan
2020-05-26 10:42 ` [PATCH v5 0/5] block: widen and check consistency of size-related BlockConf properties no-reply
2020-05-26 10:46 ` no-reply
2020-05-26 10:47 ` no-reply
2020-05-26 11:00 ` Roman Kagan [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=20200526110052.GA6355@rvkaganb.lan \
--to=rvkagan@yandex-team.ru \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kbusch@kernel.org \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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).