From: Gal Pressman <galpress@amazon.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Doug Ledford <dledford@redhat.com>
Cc: <linux-rdma@vger.kernel.org>, Leon Romanovsky <leonro@nvidia.com>,
Gal Pressman <galpress@amazon.com>
Subject: [PATCH for-next] RDMA/nldev: Add parent bdf to device information dump
Date: Tue, 3 Nov 2020 15:26:27 +0200 [thread overview]
Message-ID: <20201103132627.67642-1-galpress@amazon.com> (raw)
Add the ability to query the device's bdf through rdma tool netlink
command (in addition to the sysfs infra).
In case of virtual devices (rxe/siw), the netdev bdf will be shown.
Signed-off-by: Gal Pressman <galpress@amazon.com>
---
drivers/infiniband/core/nldev.c | 10 +++++++++-
include/uapi/rdma/rdma_netlink.h | 5 +++++
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/core/nldev.c b/drivers/infiniband/core/nldev.c
index 12d29d54a081..9704b1449c01 100644
--- a/drivers/infiniband/core/nldev.c
+++ b/drivers/infiniband/core/nldev.c
@@ -291,7 +291,15 @@ static int fill_dev_info(struct sk_buff *msg, struct ib_device *device)
else if (rdma_protocol_usnic(device, port))
ret = nla_put_string(msg, RDMA_NLDEV_ATTR_DEV_PROTOCOL,
"usnic");
- return ret;
+ if (ret)
+ return ret;
+
+ if (device->dev.parent)
+ if (nla_put_string(msg, RDMA_NLDEV_PARENT_BDF,
+ dev_name(device->dev.parent)))
+ return -EMSGSIZE;
+
+ return 0;
}
static int fill_port_info(struct sk_buff *msg,
diff --git a/include/uapi/rdma/rdma_netlink.h b/include/uapi/rdma/rdma_netlink.h
index d2f5b8396243..7495104668eb 100644
--- a/include/uapi/rdma/rdma_netlink.h
+++ b/include/uapi/rdma/rdma_netlink.h
@@ -533,6 +533,11 @@ enum rdma_nldev_attr {
RDMA_NLDEV_ATTR_RES_RAW, /* binary */
+ /*
+ * Parent device BDF (bus, device, function).
+ */
+ RDMA_NLDEV_PARENT_BDF, /* string */
+
/*
* Always the end
*/
--
2.29.1
next reply other threads:[~2020-11-03 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 13:26 Gal Pressman [this message]
2020-11-03 13:31 ` [PATCH for-next] RDMA/nldev: Add parent bdf to device information dump Parav Pandit
2020-11-03 13:45 ` Jason Gunthorpe
2020-11-03 13:57 ` Leon Romanovsky
2020-11-03 14:11 ` Gal Pressman
2020-11-03 14:22 ` Jason Gunthorpe
2020-11-03 15:45 ` Gal Pressman
2020-11-05 20:00 ` Jason Gunthorpe
2020-11-08 13:03 ` Gal Pressman
2020-11-08 14:36 ` Parav Pandit
2020-11-08 23:49 ` Jason Gunthorpe
2020-11-09 5:09 ` Leon Romanovsky
2020-11-09 9:03 ` Gal Pressman
2020-11-09 11:55 ` Leon Romanovsky
2020-11-09 12:27 ` Gal Pressman
2020-11-09 12:32 ` Leon Romanovsky
2020-11-09 12:47 ` Gal Pressman
2020-11-09 13:02 ` Leon Romanovsky
2020-11-09 13:52 ` Gal Pressman
2020-11-09 14:12 ` Leon Romanovsky
2020-11-09 9:03 ` Gal Pressman
2020-11-09 17:57 ` Jason Gunthorpe
2020-11-10 7:49 ` Gal Pressman
2020-11-10 13:41 ` Jason Gunthorpe
2020-11-10 13:54 ` Leon Romanovsky
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=20201103132627.67642-1-galpress@amazon.com \
--to=galpress@amazon.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.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