All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Shkolnyy <kshk@linux.ibm.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, dtatulea@nvidia.com,
	Cindy Lu <lulu@redhat.com>, eperezma <eperezma@redhat.com>
Subject: Re: VDPA MAC address problem
Date: Thu, 20 Mar 2025 11:45:02 -0500	[thread overview]
Message-ID: <fa821773-225f-4e2b-8642-72d269802d96@linux.ibm.com> (raw)
In-Reply-To: <CACGkMEvrOx=jN9iULQ_svJdqKt3guJuZNEOan9-eeLirLk7_=g@mail.gmail.com>

On 3/19/2025 19:58, Jason Wang wrote:
> On Thu, Mar 20, 2025 at 12:34 AM Konstantin Shkolnyy <kshk@linux.ibm.com> wrote:
>> Upon reading this forum, I see that VHOST_VDPA_SET_CONFIG is
>> “deprecated”, and so VIRTIO_NET_CTRL_MAC_ADDR_SET must be the right
>> method, but it’s apparently called too late.
> 
> VHOST_VDPA_SET_CONFIG requires the vDPA parent support which is not
> necessarily there.

The mlx5 driver doesn't do anything for VHOST_VDPA_SET_CONFIG. Intel's 
driver, however, apparently stores the configuration. So, it appears, 
Intel will avoid the problem... Perhaps mlx5 could do the same so that 
QEMU can set the address before it starts the VM (QEMU doesn't have to 
later let the VM change the config). Conceptually, setting the address 
by QEMU cmdline doesn't look different from setting it by "vdpa dev add".



  parent reply	other threads:[~2025-03-20 16:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 16:34 VDPA MAC address problem Konstantin Shkolnyy
2025-03-20  0:58 ` Jason Wang
2025-03-20  6:54   ` Eugenio Perez Martin
2025-03-20 13:59     ` Konstantin Shkolnyy
2025-03-20  9:14   ` Cindy Lu
2025-03-20 14:18   ` Konstantin Shkolnyy
2025-03-21  1:23     ` Jason Wang
2025-03-20 16:45   ` Konstantin Shkolnyy [this message]
2025-03-21  1:22     ` Jason Wang
2025-03-21  4:29       ` Konstantin Shkolnyy
2025-03-21  6:18         ` Cindy Lu
2025-03-24  4:04         ` Jason Wang

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=fa821773-225f-4e2b-8642-72d269802d96@linux.ibm.com \
    --to=kshk@linux.ibm.com \
    --cc=dtatulea@nvidia.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lulu@redhat.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 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.