From: "Ye, MingjinX" <mingjinx.ye@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"Gupta, Nipun" <nipun.gupta@amd.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yang, Qiming" <qiming.yang@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Chenbo Xia <chenbox@nvidia.com>
Subject: RE: [PATCH] vfio: add get device info API
Date: Wed, 15 Nov 2023 07:54:20 +0000 [thread overview]
Message-ID: <SN7PR11MB7139A4A5A05185509BE6BF93E5B1A@SN7PR11MB7139.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231114161203.6e1be299@hermes.local>
Hi Nipun and all,
Introducing new rte_vfio_get_device_info api in EAL to support getting information about devices.
Could you provide some suggestions?
Thanks,
Mingjin
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Wednesday, November 15, 2023 8:12 AM
> To: Ye, MingjinX <mingjinx.ye@intel.com>
> Cc: dev@dpdk.org; Yang, Qiming <qiming.yang@intel.com>;
> stable@dpdk.org; Burakov, Anatoly <anatoly.burakov@intel.com>
> Subject: Re: [PATCH] vfio: add get device info API
>
> On Tue, 14 Nov 2023 10:48:16 +0000
> Mingjin Ye <mingjinx.ye@intel.com> wrote:
>
> > +/**
> > + * Get device information
> > + *
> > + * This function is only relevant to linux and will return
> > + * an error on BSD.
> > + *
> > + * @param sysfs_base
> > + * sysfs path prefix.
> > + *
> > + * @param dev_addr
> > + * device location.
> > + *
> > + * @param vfio_dev_fd
> > + * VFIO fd.
> > + *
> > + * @param device_info
> > + * Device information.
> > + *
> > + * @return
> > + * 0 on success.
> > + * <0 on failure.
> > + */
> > +int
> > +rte_vfio_get_device_info(const char *sysfs_base, const char *dev_addr,
> > + int *vfio_dev_fd, struct vfio_device_info
> *device_info);
>
> New api's must be experimental.
> Or is this just internal?
New api is experimental.
next prev parent reply other threads:[~2023-11-15 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 10:48 Mingjin Ye
2023-11-15 0:12 ` Stephen Hemminger
2023-11-15 7:54 ` Ye, MingjinX [this message]
2023-11-15 15:09 ` Stephen Hemminger
2023-11-24 14:09 ` Burakov, Anatoly
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 10:23 Mingjin Ye
2023-11-15 6:13 ` Chenbo Xia
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=SN7PR11MB7139A4A5A05185509BE6BF93E5B1A@SN7PR11MB7139.namprd11.prod.outlook.com \
--to=mingjinx.ye@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=nipun.gupta@amd.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).