From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, dtatulea@nvidia.com, mst@redhat.com,
jasowang@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH 2/2] vdpa_sim_net: Add the support of set mac address
Date: Tue, 11 Jun 2024 13:32:33 +0800 [thread overview]
Message-ID: <20240611053239.516996-2-lulu@redhat.com> (raw)
In-Reply-To: <20240611053239.516996-1-lulu@redhat.com>
Add the function to support setting the MAC address.
For vdpa_sim_net, the driver will write the MAC address
to the config space, and other devices can implement
their own functions to support this.
Signed-off-by: Cindy Lu <lulu@redhat.com>
---
drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/drivers/vdpa/vdpa_sim/vdpa_sim_net.c b/drivers/vdpa/vdpa_sim/vdpa_sim_net.c
index cfe962911804..e961a08341c2 100644
--- a/drivers/vdpa/vdpa_sim/vdpa_sim_net.c
+++ b/drivers/vdpa/vdpa_sim/vdpa_sim_net.c
@@ -414,6 +414,21 @@ static void vdpasim_net_get_config(struct vdpasim *vdpasim, void *config)
net_config->status = cpu_to_vdpasim16(vdpasim, VIRTIO_NET_S_LINK_UP);
}
+static int vdpasim_net_set_mac(struct vdpa_mgmt_dev *mdev,
+ struct vdpa_device *dev,
+ const struct vdpa_dev_set_config *config)
+{
+ struct vdpasim *vdpasim = container_of(dev, struct vdpasim, vdpa);
+
+ struct virtio_net_config *vio_config = vdpasim->config;
+
+ if (config->mask & (1 << VDPA_ATTR_DEV_NET_CFG_MACADDR)) {
+ memcpy(vio_config->mac, config->net.mac, ETH_ALEN);
+ return 0;
+ }
+ return -EINVAL;
+}
+
static void vdpasim_net_setup_config(struct vdpasim *vdpasim,
const struct vdpa_dev_set_config *config)
{
@@ -510,7 +525,8 @@ static void vdpasim_net_dev_del(struct vdpa_mgmt_dev *mdev,
static const struct vdpa_mgmtdev_ops vdpasim_net_mgmtdev_ops = {
.dev_add = vdpasim_net_dev_add,
- .dev_del = vdpasim_net_dev_del
+ .dev_del = vdpasim_net_dev_del,
+ .set_mac = vdpasim_net_set_mac
};
static struct virtio_device_id id_table[] = {
--
2.45.0
next prev parent reply other threads:[~2024-06-11 5:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 5:32 [PATCH 1/2] vdpa: support set mac address from vdpa tool Cindy Lu
2024-06-11 5:32 ` Cindy Lu [this message]
2024-06-12 1:58 ` Jakub Kicinski
2024-06-12 6:29 ` Jiri Pirko
2024-06-12 7:15 ` Michael S. Tsirkin
2024-06-12 7:22 ` Jiri Pirko
2024-06-13 6:49 ` Michael S. Tsirkin
2024-06-13 7:21 ` Jiri Pirko
2024-06-13 7:50 ` Michael S. Tsirkin
2024-06-13 14:46 ` Jiri Pirko
2024-06-17 1:48 ` Jason Wang
2024-06-17 2:57 ` Parav Pandit
2024-06-17 9:39 ` Jiri Pirko
2024-06-17 9:44 ` Parav Pandit
2024-06-17 11:39 ` Jiri Pirko
2024-06-17 11:48 ` Parav Pandit
2024-06-17 13:02 ` Jiri Pirko
2024-06-17 13:47 ` Michael S. Tsirkin
2024-06-17 15:20 ` Jakub Kicinski
2024-06-17 16:20 ` Michael S. Tsirkin
2024-06-17 16:44 ` Jakub Kicinski
2024-06-18 10:39 ` Michael S. Tsirkin
2024-06-19 13:10 ` Cindy Lu
2024-06-12 7:12 ` Michael S. Tsirkin
2024-06-13 6:44 ` Cindy Lu
2024-06-13 6:59 ` Michael S. Tsirkin
2024-06-13 13:29 ` 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=20240611053239.516996-2-lulu@redhat.com \
--to=lulu@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).