Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: "Michael S . Tsirkin" <mst@redhat.com>
Subject: [PATCH v3 0/1] [PATCH v3] device-types/blk/description.tex: Allow longer device IDs to be returned
Date: Tue,  8 Sep 2026 10:40:49 +0100	[thread overview]
Message-ID: <20260908094050.915173-1-rjones@redhat.com> (raw)

v3 considerably simplifies everything.  We now use the feature bit
(VIRTIO_BLK_F_LONG_ID) to decide if the driver will provide a 20 or
248 byte buffer to VIRTIO_BLK_T_GET_ID.

VIRTIO_BLK_T_GET_LONG_ID has been dropped.

There is a working implementation of this here:

https://github.com/rwmjones/virtio-spec/commits/2026-virtio-blk-long-id/
https://gitlab.com/rwmjones/qemu/-/commits/2026-virtio-blk-long-id?ref_type=heads
https://github.com/rwmjones/linux/commits/2026-virtio-blk-long-id/

Rich.

Richard W.M. Jones (1):
  device-types/blk/description.tex: Allow longer device IDs to be
    returned

 device-types/blk/description.tex | 27 ++++++++++++++++++++++++---
 1 file changed, 24 insertions(+), 3 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-09-08  9:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  9:40 Richard W.M. Jones [this message]
2026-09-08  9:40 ` [PATCH v3 1/1] device-types/blk/description.tex: Allow longer device IDs to be returned Richard W.M. Jones
2026-09-08 10:57   ` Michael S. Tsirkin
2026-09-08 11:51     ` Richard W.M. Jones
2026-09-08 14:16       ` Michael S. Tsirkin
2026-09-08 15:14   ` Stefan Hajnoczi
2026-09-08 15:46     ` Richard W.M. Jones
2026-09-08 16:43       ` Michael S. Tsirkin
2026-09-09  2:12         ` Demi Marie Obenour
2026-09-09  3:34           ` Parav Pandit
2026-09-09  7:07             ` Michael S. Tsirkin
2026-09-09  7:05           ` Michael S. Tsirkin
2026-09-08 16:25     ` Michael S. Tsirkin

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=20260908094050.915173-1-rjones@redhat.com \
    --to=rjones@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtio-comment@lists.linux.dev \
    /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