From: Jason Wang <jasowang@redhat.com>
To: Cindy Lu <lulu@redhat.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/3] virtio_net: Add the check for vdpa's mac address
Date: Wed, 7 Aug 2024 10:35:52 +0800 [thread overview]
Message-ID: <CACGkMEvCSKfahpBQLAMmSzdFN-QPhg5Zx+UQVrFX0HsWybZZNA@mail.gmail.com> (raw)
In-Reply-To: <CACLfguU47TPw5=GpS93AMWEYcy95JJ6+uG-PYpdmeD=hrKGa1Q@mail.gmail.com>
On Tue, Aug 6, 2024 at 5:44 PM Cindy Lu <lulu@redhat.com> wrote:
>
> On Tue, 6 Aug 2024 at 11:07, Jason Wang <jasowang@redhat.com> wrote:
> >
> > On Tue, Aug 6, 2024 at 8:58 AM Cindy Lu <lulu@redhat.com> wrote:
> > >
> > > When using a VDPA device, it is important to ensure that
> > > the MAC address in the hardware matches the MAC address
> > > from the QEMU command line.
> > > This will allow the device to boot.
> > >
> > > Signed-off-by: Cindy Lu <lulu@redhat.com>
> > > ---
> > > hw/net/virtio-net.c | 33 +++++++++++++++++++++++++++++----
> > > 1 file changed, 29 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> > > index 9c7e85caea..7f51bd0dd3 100644
> > > --- a/hw/net/virtio-net.c
> > > +++ b/hw/net/virtio-net.c
> > > @@ -3579,12 +3579,36 @@ static bool failover_hide_primary_device(DeviceListener *listener,
> > > /* failover_primary_hidden is set during feature negotiation */
> > > return qatomic_read(&n->failover_primary_hidden);
> > > }
> > > +static bool virtio_net_check_vdpa_mac(NetClientState *nc, VirtIONet *n, MACAddr *cmdline_mac,
> > > + Error **errp)
> > > +{
> > > + struct virtio_net_config hwcfg = {};
> > > + static const MACAddr zero = { .a = { 0, 0, 0, 0, 0, 0 } };
> > > +
> > > + vhost_net_get_config(get_vhost_net(nc->peer), (uint8_t *)&hwcfg, ETH_ALEN);
> > > +
> > > + /*
> > > + * For VDPA device: Only two situations are acceptable:
> > > + * 1.The hardware MAC address is the same as the QEMU command line MAC
> > > + * address, and both of them are not 0.
> >
> > I guess there should be a bullet 2?
> >
> yes, there is a section 2, will change this code here
> Thanks
> cindy
> > > + */
> > > +
> > > + if (memcmp(&hwcfg.mac, &zero, sizeof(MACAddr)) != 0) {
> > > + if ((memcmp(&hwcfg.mac, cmdline_mac, sizeof(MACAddr)) == 0)) {
> > > + return true;
> > > + }
> > > + }
> > > + error_setg(errp, "vDPA device's mac != the mac address from qemu cmdline"
> > > + "Please check the the vdpa device's setting.");
> >
> > For error messages I think it's better to use english instead of "!="
> > to describe the issue.
> >
> > >
> > > + return false;
> > > +}
> > > static void virtio_net_device_realize(DeviceState *dev, Error **errp)
> > > {
> > > VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> > > VirtIONet *n = VIRTIO_NET(dev);
> > > NetClientState *nc;
> > > + MACAddr macaddr_cmdline;
> > > int i;
> > >
> > > if (n->net_conf.mtu) {
> > > @@ -3692,6 +3716,7 @@ static void virtio_net_device_realize(DeviceState *dev, Error **errp)
> > > virtio_net_add_queue(n, 0);
> > >
> > > n->ctrl_vq = virtio_add_queue(vdev, 64, virtio_net_handle_ctrl);
> > > + memcpy(&macaddr_cmdline, &n->nic_conf.macaddr, sizeof(n->mac));
> > > qemu_macaddr_default_if_unset(&n->nic_conf.macaddr);
> > > memcpy(&n->mac[0], &n->nic_conf.macaddr, sizeof(n->mac));
> > > n->status = VIRTIO_NET_S_LINK_UP;
> > > @@ -3739,10 +3764,10 @@ static void virtio_net_device_realize(DeviceState *dev, Error **errp)
> > > nc->rxfilter_notify_enabled = 1;
> > >
> > > if (nc->peer && nc->peer->info->type == NET_CLIENT_DRIVER_VHOST_VDPA) {
> > > - struct virtio_net_config netcfg = {};
> > > - memcpy(&netcfg.mac, &n->nic_conf.macaddr, ETH_ALEN);
> > > - vhost_net_set_config(get_vhost_net(nc->peer),
> > > - (uint8_t *)&netcfg, 0, ETH_ALEN, VHOST_SET_CONFIG_TYPE_FRONTEND);
> > > + if (!virtio_net_check_vdpa_mac(nc, n, &macaddr_cmdline, errp)) {
> > > + virtio_cleanup(vdev);
> > > + return;
> > > + }
> >
> > Any reason we remove vhost_net_set_config() here? It is not described
> > in the commit or does it belong to another patch?
> >
> > Thanks
> >
> as we discussed before, the MAC address in hardware should have a
> "higher priority"
> than the MAC address in qemu cmdline. So I remove the set_config there,
> the MAC address from the hardware will overwrite the MAC in qemu
> cmdline. so don't need to set_config to hardware now
Probably, but I meant it needs to be a separate patch.
For example the title said "add ...." but here it's a removal of something.
Thanks
> Thanks,
> cindy
> > > }
> > > QTAILQ_INIT(&n->rsc_chains);
> > > n->qdev = dev;
> > > --
> > > 2.45.0
> > >
> >
>
next prev parent reply other threads:[~2024-08-07 2:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 0:58 [PATCH 1/3] virtio_net: Add the check for vdpa's mac address Cindy Lu
2024-08-06 0:58 ` [PATCH 2/3] virtio_net: Add the check for vdpa " Cindy Lu
2024-08-06 3:08 ` Jason Wang
2024-08-06 0:58 ` [PATCH 3/3] virtio_net: remove the unnecessary check in get_config Cindy Lu
2024-08-06 3:09 ` Jason Wang
2024-08-06 9:47 ` Cindy Lu
2024-08-06 3:06 ` [PATCH 1/3] virtio_net: Add the check for vdpa's mac address Jason Wang
2024-08-06 9:43 ` Cindy Lu
2024-08-06 11:12 ` Yan Vugenfirer
2024-08-09 9:14 ` Cindy Lu
2024-08-07 2:35 ` Jason Wang [this message]
2024-08-09 9:14 ` Cindy Lu
2024-08-06 13:30 ` Michael S. Tsirkin
2024-08-09 9:15 ` Cindy Lu
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=CACGkMEvCSKfahpBQLAMmSzdFN-QPhg5Zx+UQVrFX0HsWybZZNA@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=lulu@redhat.com \
--cc=mst@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 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).