From: Jason Gunthorpe <jgg@nvidia.com>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: Leon Romanovsky <leon@kernel.org>,
brett.creeley@amd.com, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, drivers@pensando.io,
jiri@resnulli.us
Subject: Re: [PATCH v8 net-next 10/14] pds_core: add auxiliary_bus devices
Date: Fri, 14 Apr 2023 09:37:37 -0300 [thread overview]
Message-ID: <ZDlJES8t0nivTQLz@nvidia.com> (raw)
In-Reply-To: <fc39973a-3f57-87d0-ff46-15a09e9b5f58@amd.com>
On Sat, Apr 01, 2023 at 01:15:03PM -0700, Shannon Nelson wrote:
> We have a PF device that has an adminq, VF devices that don't have an
> adminq, and the adminq is needed for some basic setup before the rest of the
> vDPA driver can use the VF. To access the PF's adminq we set up an
> auxiliary device per feature in each VF - but currently only offer one
> feature (vDPA) and no sub-devices yet. We're trying to plan for the future.
It is the same remark I gave for the VFIO integration, the bound VF
driver should use pci_iov_get_pf_drvdata() to reach to its PF driver
and operate the admin queue. Make sure to read the comment of the
function to lock it properly.
There should not be a parallel aux device for the VF device, the
purpose of the aux device is not to allow you to find things like
admin queue objects, it is to represent a slice of device
functionality that doesn't already have a struct device
representation.
Drivers should not attempt to 'dual bind' aux device and pci device as
the original vfio patches tried to do.
Jason
next prev parent reply other threads:[~2023-04-14 12:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 23:46 [PATCH v8 net-next 00/14] pds_core driver Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 01/14] pds_core: initial framework for pds_core PF driver Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 02/14] pds_core: add devcmd device interfaces Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 03/14] pds_core: health timer and workqueue Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 04/14] pds_core: add devlink health facilities Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 05/14] pds_core: set up device and adminq Shannon Nelson
2023-04-01 5:07 ` Jakub Kicinski
2023-04-01 19:48 ` Shannon Nelson
2023-04-03 20:37 ` Jakub Kicinski
2023-03-30 23:46 ` [PATCH v8 net-next 06/14] pds_core: Add adminq processing and commands Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 07/14] pds_core: add FW update feature to devlink Shannon Nelson
2023-04-01 5:09 ` Jakub Kicinski
2023-04-01 19:49 ` Shannon Nelson
2023-04-04 14:48 ` Jakub Kicinski
2023-03-30 23:46 ` [PATCH v8 net-next 08/14] pds_core: set up the VIF definitions and defaults Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 09/14] pds_core: add initial VF device handling Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 10/14] pds_core: add auxiliary_bus devices Shannon Nelson
2023-04-01 18:27 ` Leon Romanovsky
2023-04-01 20:15 ` Shannon Nelson
2023-04-03 6:18 ` Leon Romanovsky
2023-04-04 21:44 ` Shannon Nelson
2023-04-05 6:07 ` Leon Romanovsky
2023-04-05 17:17 ` Shannon Nelson
2023-04-14 12:37 ` Jason Gunthorpe [this message]
2023-03-30 23:46 ` [PATCH v8 net-next 11/14] pds_core: devlink params for enabling VIF support Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 12/14] pds_core: add the aux client API Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 13/14] pds_core: publish events to the clients Shannon Nelson
2023-03-30 23:46 ` [PATCH v8 net-next 14/14] pds_core: Kconfig and pds_core.rst Shannon Nelson
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=ZDlJES8t0nivTQLz@nvidia.com \
--to=jgg@nvidia.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.