All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Alberto Faria" <afaria@redhat.com>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
Subject: Re: [PATCH 1/2] include: Add virtio-blk request flag FUA definitions
Date: Wed, 21 Oct 2026 14:37:07 +0200	[thread overview]
Message-ID: <87pkx32psc.fsf@redhat.com> (raw)
In-Reply-To: <atiukShvcKuVOuMj@redhat.com>

On Wed, Oct 21 2026, Kevin Wolf <kwolf@redhat.com> wrote:

> Am 21.10.2026 um 09:59 hat Cornelia Huck geschrieben:
>> On Wed, Oct 21 2026, Alberto Faria <afaria@redhat.com> wrote:
>> 
>> > Signed-off-by: Alberto Faria <afaria@redhat.com>
>> > ---
>> >  include/standard-headers/linux/virtio_blk.h | 13 +++++++++++--
>> >  1 file changed, 11 insertions(+), 2 deletions(-)
>> 
>> Maybe explicitly mark as *placeholder*, so it doesn't get merged
>> accidentally?
>
> What is the proper (or at least common) way to do this? Do we really
> have to wait for Linux to merge the guest driver side of virtio device
> changes before we can add the emulation in QEMU?

If we have some changes in the synced-from-Linux headers, we really need
to do a proper header sync to get them (or the next sync might remove
the changes again...) So yes, this unfortunately needs to wait for a
kernel with the changes (can be -rc)...

***

The other question (not really related to this patch set, maybe
warranting a separate discussion): Should we move the host <-> guest
interface definition to a third place that both Linux and QEMU (and any
other piece of software) can sync from? Source-of-truth is the virtio
spec, so in a perfect world QEMU should not have to wait for a Linux
kernel with the definitions to be released once it has been enshrined
there. Grabbing everything from Linux is something that did get the job
done and avoided duplicating code, but maybe it's time to revisit this.
(We obviously should keep syncing headers for actual kernel <->
userspace interfaces.)



  reply	other threads:[~2026-10-21 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  6:22 [PATCH 0/2] virtio-blk: Add support for FUA write requests Alberto Faria
2026-10-21  6:22 ` [PATCH 1/2] include: Add virtio-blk request flag FUA definitions Alberto Faria
2026-10-21  7:59   ` Cornelia Huck
2026-10-21 12:22     ` Kevin Wolf
2026-10-21 12:37       ` Cornelia Huck [this message]
2026-10-21  6:22 ` [PATCH 2/2] virtio-blk: Add support for FUA write requests Alberto Faria
2026-10-28 19:55   ` Stefan Hajnoczi

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=87pkx32psc.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=afaria@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@oss.qualcomm.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=zhao1.liu@intel.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.