From: Stefan Hajnoczi <stefanha@gmail.com>
To: Ekaterina Tumanova <tumanova@linux.vnet.ibm.com>
Cc: cornelia.huck@de.ibm.com, dahi@linux.vnet.ibm.com,
Public KVM Mailing List <qemu-devel@nongnu.org>,
borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH 2/4] blocksize: support auto-sensing of blocksizes
Date: Wed, 3 Sep 2014 16:37:57 +0100 [thread overview]
Message-ID: <20140903153757.GA30664@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1406636839-11946-3-git-send-email-tumanova@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Tue, Jul 29, 2014 at 02:27:17PM +0200, Ekaterina Tumanova wrote:
> The block device model does not impose fixed block sizes for
> access to backing devices. This patch introduces support for
> auto lookup of the block sizes of the backing block device.
>
> To achieve this, a new function blkconf_blocksizes is
> implemented. This function tries to get values
> from the block driver. If this does not work 512 is used,
> so the default excecution logic is not changed.
>
> Based on 2013 patch from Einar Lueck <elelueck@de.ibm.com>
>
> Signed-off-by: Ekaterina Tumanova <tumanova@linux.vnet.ibm.com>
> Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
> Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
> block.c | 12 ++++++++++++
> hw/block/block.c | 25 +++++++++++++++++++++++++
> hw/core/qdev-properties.c | 4 +++-
> include/block/block.h | 1 +
> include/block/block_int.h | 5 +++++
> include/hw/block/block.h | 2 ++
> 6 files changed, 48 insertions(+), 1 deletion(-)
This should be implemented as part of BlockLimits and
bdrv_refresh_limits().
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-03 15:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 12:27 [Qemu-devel] [PATCH 0/4] Geometry and blocksize support for backing devices Ekaterina Tumanova
2014-07-29 12:27 ` [Qemu-devel] [PATCH 1/4] hd-geometry.c: Integrate HDIO_GETGEO in guessing for target-s390x Ekaterina Tumanova
2014-08-20 8:19 ` Paolo Bonzini
2014-08-20 9:35 ` Christian Borntraeger
2014-08-20 13:10 ` Paolo Bonzini
2014-08-25 8:21 ` Christian Borntraeger
2014-07-29 12:27 ` [Qemu-devel] [PATCH 2/4] blocksize: support auto-sensing of blocksizes Ekaterina Tumanova
2014-09-03 15:37 ` Stefan Hajnoczi [this message]
2014-07-29 12:27 ` [Qemu-devel] [PATCH 3/4] blocksize: Add driver method to get the blocksizes Ekaterina Tumanova
2014-07-29 12:27 ` [Qemu-devel] [PATCH 4/4] blocksize: add blkconf_blocksize call to all block devices Ekaterina Tumanova
2014-09-03 15:46 ` Stefan Hajnoczi
2014-09-04 10:28 ` Ekaterina Tumanova
2014-09-17 14:00 ` Stefan Hajnoczi
2014-09-04 14:15 ` Christian Borntraeger
2014-09-17 13:56 ` Stefan Hajnoczi
2014-07-29 12:37 ` [Qemu-devel] [PATCH 0/4] Geometry and blocksize support for backing devices Christian Borntraeger
2014-11-06 15:58 ` [Qemu-devel] " Christian Borntraeger
2014-11-06 17:24 ` Paolo Bonzini
2014-11-06 19:05 ` Christian Borntraeger
2014-11-07 9:17 ` Markus Armbruster
2014-11-07 9:48 ` Christian Borntraeger
2014-11-07 15:58 ` Markus Armbruster
2014-11-07 13:39 ` Ekaterina Tumanova
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=20140903153757.GA30664@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=tumanova@linux.vnet.ibm.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).