From: Leon Romanovsky <leon@kernel.org>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: 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: Sat, 1 Apr 2023 21:27:01 +0300 [thread overview]
Message-ID: <20230401182701.GA831478@unreal> (raw)
In-Reply-To: <20230330234628.14627-11-shannon.nelson@amd.com>
On Thu, Mar 30, 2023 at 04:46:24PM -0700, Shannon Nelson wrote:
> An auxiliary_bus device is created for each vDPA type VF at VF probe
> and destroyed at VF remove. The VFs are always removed on PF remove, so
> there should be no issues with VFs trying to access missing PF structures.
>
> Signed-off-by: Shannon Nelson <shannon.nelson@amd.com>
> ---
> drivers/net/ethernet/amd/pds_core/Makefile | 1 +
> drivers/net/ethernet/amd/pds_core/auxbus.c | 142 +++++++++++++++++++++
> drivers/net/ethernet/amd/pds_core/core.h | 6 +
> drivers/net/ethernet/amd/pds_core/main.c | 36 +++++-
> include/linux/pds/pds_auxbus.h | 16 +++
> include/linux/pds/pds_common.h | 1 +
> 6 files changed, 200 insertions(+), 2 deletions(-)
> create mode 100644 drivers/net/ethernet/amd/pds_core/auxbus.c
> create mode 100644 include/linux/pds/pds_auxbus.h
I feel that this auxbus usage is still not correct.
The idea of auxiliary devices is to partition physical device (for
example PCI device) to different sub-devices, where every sub-device
belongs to different sub-system. It is not intended to create per-VF
devices.
In your case, you should create XXX vDPA auxiliary devices which are
connected in one-to-one scheme to their PCI VF counterpart.
Thanks
next prev parent reply other threads:[~2023-04-01 18:27 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 [this message]
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
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=20230401182701.GA831478@unreal \
--to=leon@kernel.org \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=jiri@resnulli.us \
--cc=kuba@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 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).