From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, mst@redhat.com, jasowang@redhat.com,
qemu-devel@nongnu.org
Subject: [PATCH v2 2/3] virtio_net: Add the 2rd acceptable situation for Mac setup.
Date: Sun, 29 Sep 2024 23:59:56 +0800 [thread overview]
Message-ID: <20240929160045.2133423-3-lulu@redhat.com> (raw)
In-Reply-To: <20240929160045.2133423-1-lulu@redhat.com>
When using a VDPA device, the following situations are
also acceptable: the hardware MAC address is not 0,
and the MAC address in the QEMU command line is 0.
Signed-off-by: Cindy Lu <lulu@redhat.com>
---
hw/net/virtio-net.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
index 7aa7308244..5c610d8078 100644
--- a/hw/net/virtio-net.c
+++ b/hw/net/virtio-net.c
@@ -3607,6 +3607,18 @@ static bool virtio_net_check_vdpa_mac(NetClientState *nc, VirtIONet *n,
if ((memcmp(&hwcfg.mac, cmdline_mac, sizeof(MACAddr)) == 0)) {
return true;
}
+ /*
+ * 2.The hardware MAC address is not 0,
+ * and the MAC address in the QEMU command line is 0.
+ * In this situation, the hardware MAC address will overwrite
+ * the QEMU command line address.
+ */
+ if (memcmp(cmdline_mac, &zero, sizeof(MACAddr)) == 0) {
+ /* overwrite the mac address with hardware address*/
+ memcpy(&n->mac[0], &hwcfg.mac, sizeof(n->mac));
+ memcpy(&n->nic_conf.macaddr, &hwcfg.mac, sizeof(n->mac));
+ return true;
+ }
}
error_setg(errp,
--
2.45.0
next prev parent reply other threads:[~2024-09-29 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 15:59 [PATCH v2 0/3] virtio_net: Add the check for vdpa's mac address Cindy Lu
2024-09-29 15:59 ` [PATCH v2 1/3] " Cindy Lu
2024-10-09 8:28 ` Jason Wang
2024-09-29 15:59 ` Cindy Lu [this message]
2024-10-09 8:29 ` [PATCH v2 2/3] virtio_net: Add the 2rd acceptable situation for Mac setup Jason Wang
2024-10-14 1:50 ` Cindy Lu
2024-09-29 15:59 ` [PATCH v2 3/3] virtio_net: Add the 3rd " Cindy Lu
2024-10-09 8:30 ` Jason Wang
2024-10-14 1:50 ` 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=20240929160045.2133423-3-lulu@redhat.com \
--to=lulu@redhat.com \
--cc=jasowang@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).