From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Daniel Palmer <daniel@thingy.jp>
Cc: angelo@kernel-space.org, bmeng.cn@gmail.com, u-boot@lists.denx.de
Subject: Re: [PATCH v3 4/5] virtio: blk: Fix converting the vendor id to a string
Date: Mon, 13 Apr 2026 05:34:34 +0800 [thread overview]
Message-ID: <adwP6m1zDjUQWAl0@google.com> (raw)
In-Reply-To: <20260408220928.3328551-5-daniel@thingy.jp>
Hi Daniel,
On Thu, Apr 09, 2026 at 07:09:27AM +0900, Daniel Palmer wrote:
> Currently we are trying to work out if the vendor id is from
> a virtio-mmio device and then casting a u32 to a char* and using
> it as a C-string. By chance there is usually a zero after the u32
> and it works.
>
> Since the vendor id we are trying to convert to a string is QEMU's
> just define a value for the QEMU vendor id, check if the vendor
> id matches and then use a predefined string for "QEMU".
>
> I don't think we should have been assumming all virtio-mmio vendor
> ids are printable ASCII chars in the first place so do this special
> casing just for QEMU. If the vendor id isn't QEMU print the hex
> value of it.
>
> Signed-off-by: Daniel Palmer <daniel@thingy.jp>
> ---
> drivers/virtio/virtio_blk.c | 12 +++++-------
> include/virtio_mmio.h | 2 ++
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/virtio/virtio_blk.c b/drivers/virtio/virtio_blk.c
> index 3dd0cf36268b..d876c40deb05 100644
> --- a/drivers/virtio/virtio_blk.c
> +++ b/drivers/virtio/virtio_blk.c
> @@ -11,6 +11,7 @@
> #include <part.h>
> #include <virtio_types.h>
> #include <virtio.h>
> +#include <virtio_mmio.h>
> #include <virtio_ring.h>
> #include <linux/log2.h>
> #include "virtio_blk.h"
> @@ -164,14 +165,11 @@ static int virtio_blk_bind(struct udevice *dev)
> return devnum;
> desc->devnum = devnum;
> desc->part_type = PART_TYPE_UNKNOWN;
> - /*
> - * virtio mmio transport supplies string identification for us,
> - * while pci trnasport uses a 2-byte subvendor value.
> - */
> - if (uc_priv->vendor >> 16)
> - sprintf(desc->vendor, "%s", (char *)&uc_priv->vendor);
> +
> + if (uc_priv->vendor == VIRTIO_MMIO_VENDOR_QEMU)
> + strcpy(desc->vendor, "QEMU");
Is there a chance that other non qemu virtio-mmio devices also use a
4 character string for their vendor ID? If so, this patch will regress
their output from a human-readable string to a raw hex value.
Regards,
Kuan-Wei
> else
> - sprintf(desc->vendor, "%04x", uc_priv->vendor);
> + sprintf(desc->vendor, "%08x", uc_priv->vendor);
> desc->bdev = dev;
>
> /* Indicate what driver features we support */
> diff --git a/include/virtio_mmio.h b/include/virtio_mmio.h
> index 8c072826db55..cc59bc516c2c 100644
> --- a/include/virtio_mmio.h
> +++ b/include/virtio_mmio.h
> @@ -5,6 +5,8 @@
>
> #include <linux/types.h>
>
> +#define VIRTIO_MMIO_VENDOR_QEMU 0x554d4551
> +
> struct virtio_mmio_plat {
> phys_addr_t base;
> };
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-04-12 21:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 22:09 [PATCH v3 0/5] Add virtio-mmio support to m68k virt machine Daniel Palmer
2026-04-08 22:09 ` [PATCH v3 1/5] sysreset: qemu virt: Use __raw_writel() Daniel Palmer
2026-04-11 16:28 ` Simon Glass
2026-04-11 19:40 ` Angelo Dureghello
2026-04-08 22:09 ` [PATCH v3 2/5] m68k: Fix writew(), writel(), readw(), readl() endianness for classic m68k Daniel Palmer
2026-04-11 16:28 ` Simon Glass
2026-04-11 21:07 ` Angelo Dureghello
2026-04-12 0:59 ` Daniel Palmer
2026-04-08 22:09 ` [PATCH v3 3/5] virtio: mmio: Allow instantiation via platform data Daniel Palmer
2026-04-11 16:28 ` Simon Glass
2026-04-11 21:15 ` Angelo Dureghello
2026-04-12 5:12 ` Daniel Palmer
2026-04-08 22:09 ` [PATCH v3 4/5] virtio: blk: Fix converting the vendor id to a string Daniel Palmer
2026-04-11 20:30 ` Simon Glass
2026-04-12 21:34 ` Kuan-Wei Chiu [this message]
2026-04-12 21:47 ` Daniel Palmer
2026-04-12 22:00 ` Kuan-Wei Chiu
2026-04-12 22:05 ` Daniel Palmer
2026-04-08 22:09 ` [PATCH v3 5/5] board: qemu: m68k: Create virtio mmio instances Daniel Palmer
2026-04-11 20:28 ` Angelo Dureghello
2026-04-12 6:42 ` Daniel Palmer
2026-04-11 20:31 ` Simon Glass
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=adwP6m1zDjUQWAl0@google.com \
--to=visitorckw@gmail.com \
--cc=angelo@kernel-space.org \
--cc=bmeng.cn@gmail.com \
--cc=daniel@thingy.jp \
--cc=u-boot@lists.denx.de \
/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.