All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Daniel Verkamp <dverkamp@chromium.org>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
	mst@redhat.com, virtualization@lists.linux-foundation.org,
	virtio-dev@lists.linux.dev, oren@nvidia.com, parav@nvidia.com
Subject: Re: [PATCH 1/1] virtio-blk: Add description for blk_size field
Date: Tue, 8 Oct 2024 16:09:34 -0400	[thread overview]
Message-ID: <20241008200934.GA22682@fedora.redhat.com> (raw)
In-Reply-To: <CABVzXAmxuVngKjNvc9AsnkuNcOK+7JeEuBE9CDaMxAA=b3f=fw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

On Wed, Oct 02, 2024 at 04:56:10PM -0700, Daniel Verkamp wrote:
> (Perhaps u-boot's driver does not work with the QEMU's virtio-blk
> device with certain storage configurations, per Stefan's note, but
> that is again just one device implementation.)

Yes, IOERR only happens under certain conditions: when --device
virtio-blk-pci,logical_block_size=<size> is configured. When that's not
the case, QEMU buffers as necessary to adjust for guest block size vs
host block size differences without errors.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2024-10-08 20:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 14:52 [PATCH 1/1] virtio-blk: Add description for blk_size field Max Gurtovoy
2024-09-25 20:57 ` Daniel Verkamp
2024-09-25 23:42   ` Max Gurtovoy
2024-09-26 21:44     ` Daniel Verkamp
2024-09-28  0:22       ` Max Gurtovoy
2024-10-01  1:45         ` Daniel Verkamp
2024-10-02 13:42           ` Stefan Hajnoczi
2024-10-02 23:56           ` Daniel Verkamp
2024-10-06 11:35             ` Max Gurtovoy
2024-10-08  1:58               ` Daniel Verkamp
2024-10-08 20:09             ` Stefan Hajnoczi [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=20241008200934.GA22682@fedora.redhat.com \
    --to=stefanha@redhat.com \
    --cc=dverkamp@chromium.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=mst@redhat.com \
    --cc=oren@nvidia.com \
    --cc=parav@nvidia.com \
    --cc=virtio-dev@lists.linux.dev \
    --cc=virtualization@lists.linux-foundation.org \
    /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.