From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
agraf@suse.de, qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
jfrei@linux.vnet.ibm.com, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH/RFC] block: Ensure that block size constraints are considered
Date: Wed, 21 Nov 2012 17:03:57 +0100 [thread overview]
Message-ID: <50ACFB6D.8040106@redhat.com> (raw)
In-Reply-To: <50AC9B96.9070908@redhat.com>
Il 21/11/2012 10:15, Kevin Wolf ha scritto:
>> > + if ((bs->open_flags & BDRV_O_NOCACHE)) {
>> > + bs->file->buffer_alignment = align;
>> > + }
> Any reason to restrict this to BDRV_O_NOCACHE?
>
> There have been patches to change the BDRV_O_NOCACHE flag from the
> monitor, in which case bdrv_set_buffer_alignment() wouldn't be called
> anew and O_DIRECT requests start to fail again.
>
bdrv_set_buffer_alignment() is completely broken. It should set host
alignment, but in fact it is passed the guest alignment.
In practice, we only support logical_block_size matching the host's or
bigger (which is unsafe due to torn writes, but works).
So I suggest that we just look at writes outside the device models, and
"fix" them to always read a multiple of 4k.
Paolo
next prev parent reply other threads:[~2012-11-21 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 8:58 [Qemu-devel] [PATCH/RFC] block: Ensure that block size constraints are considered Christian Borntraeger
2012-11-21 9:15 ` Kevin Wolf
2012-11-21 10:00 ` Christian Borntraeger
2012-11-21 11:24 ` Heinz Graalfs
2012-11-21 16:03 ` Paolo Bonzini [this message]
2012-11-22 12:03 ` Christian Borntraeger
2012-11-23 10:45 ` Heinz Graalfs
2012-12-07 20:26 ` Heinz Graalfs
2012-12-10 8:55 ` Kevin Wolf
2012-12-11 9:58 ` Heinz Graalfs
2012-12-11 10:30 ` Kevin Wolf
2012-12-11 13:53 ` Heinz Graalfs
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=50ACFB6D.8040106@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--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.