qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eugenio Perez Martin <eperezma@redhat.com>
To: Konstantin Shkolnyy <kshk@linux.ibm.com>
Cc: jasowang@redhat.com, akihiko.odaki@daynix.com,
	qemu-devel@nongnu.org,  mjrosato@linux.ibm.com
Subject: Re: [PATCH] vdpa: Allow VDPA to work on big-endian machine
Date: Mon, 16 Jun 2025 08:19:04 +0200	[thread overview]
Message-ID: <CAJaqyWcPHdEsQMLHUyZ6MYMtppwiPBgmJP9JzQrppL8k5rPnCA@mail.gmail.com> (raw)
In-Reply-To: <20250614224422.1595301-1-kshk@linux.ibm.com>

On Sun, Jun 15, 2025 at 12:46 AM Konstantin Shkolnyy <kshk@linux.ibm.com> wrote:
>
> After commit 0caed25cd171 vhost_vdpa_net_load_vlan() started seeing
> VIRTIO_NET_F_CTRL_VLAN flag and making 4096 calls to the kernel with
> VIRTIO_NET_CTRL_VLAN_ADD command. However, it forgot to convert the
> 16-bit VLAN IDs to LE format. On BE machine, the kernel calls failed
> when they saw "VLAN IDs" greater than 4095, and QEMU then said:
> "unable to start vhost net: 5: falling back on userspace virtio", and
> VDPA became disabled.
>
> Convert the VLAN ID to LE before putting it into virtio queue.
>
> Signed-off-by: Konstantin Shkolnyy <kshk@linux.ibm.com>

Good catch! You should add the Fixes: tag though :). With that,

Acked-by: Eugenio Pérez <eperezma@redhat.com>

> ---
>  net/vhost-vdpa.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/net/vhost-vdpa.c b/net/vhost-vdpa.c
> index 58d738945d..99c9eb42b9 100644
> --- a/net/vhost-vdpa.c
> +++ b/net/vhost-vdpa.c
> @@ -1173,9 +1173,10 @@ static int vhost_vdpa_net_load_single_vlan(VhostVDPAState *s,
>                                             struct iovec *in_cursor,
>                                             uint16_t vid)
>  {
> +    __le16 vid_le = cpu_to_le16(vid);
>      const struct iovec data = {
> -        .iov_base = &vid,
> -        .iov_len = sizeof(vid),
> +        .iov_base = &vid_le,
> +        .iov_len = sizeof(vid_le),
>      };
>      ssize_t r = vhost_vdpa_net_load_cmd(s, out_cursor, in_cursor,
>                                          VIRTIO_NET_CTRL_VLAN,
> --
> 2.34.1
>
>



  parent reply	other threads:[~2025-06-16  6:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14 22:44 [PATCH] vdpa: Allow VDPA to work on big-endian machine Konstantin Shkolnyy
2025-06-16  2:49 ` Jason Wang
2025-06-16  6:19 ` Eugenio Perez Martin [this message]
2025-06-16  8:56 ` Akihiko Odaki
  -- strict thread matches above, loose matches on Subject: below --
2025-02-11 16:19 [PATCH] vdpa: Allow vDPA " Konstantin Shkolnyy
2025-02-12 13:38 ` Eugenio Perez Martin
2025-02-12 14:47   ` Konstantin Shkolnyy
2025-02-12 14:52 ` Philippe Mathieu-Daudé
2025-02-12 17:24   ` Konstantin Shkolnyy
2025-02-12 18:07     ` Philippe Mathieu-Daudé
2025-02-12 20:01       ` Konstantin Shkolnyy
2025-02-18 13:27         ` Konstantin Shkolnyy
2025-02-18 14:02           ` Philippe Mathieu-Daudé
2025-02-19  0:29             ` Jason Wang
2025-02-20 15:57 ` Michael S. Tsirkin
2025-02-21  3:40   ` Konstantin Shkolnyy

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=CAJaqyWcPHdEsQMLHUyZ6MYMtppwiPBgmJP9JzQrppL8k5rPnCA@mail.gmail.com \
    --to=eperezma@redhat.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=jasowang@redhat.com \
    --cc=kshk@linux.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).