From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Kevin Tian <kevin.tian@intel.com>,
kvm@vger.kernel.org, Longfang Liu <liulongfang@huawei.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Yishai Hadas <yishaih@nvidia.com>
Cc: Abhishek Sahu <abhsahu@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>
Subject: [PATCH v3 0/2] Remove vfio_device_get_from_dev()
Date: Wed, 4 May 2022 16:01:46 -0300 [thread overview]
Message-ID: <0-v3-4adf6c1b8e7c+170-vfio_get_from_dev_jgg@nvidia.com> (raw)
Use drvdata instead of searching to find the struct vfio_device for the
pci_driver callbacks.
This applies on top of the gvt series and at least rc3 - there are no
conflicts with the mdev vfio_group series, or the iommu series.
v2:
- Directly access the drvdata from vfio_pci_core by making drvdata always
point to the core struct. This will help later patches adding PM
callbacks as well.
v1: https://lore.kernel.org/r/0-v2-0f36bcf6ec1e+64d-vfio_get_from_dev_jgg@nvidia.com
Cc: Abhishek Sahu <abhsahu@nvidia.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Jason Gunthorpe (2):
vfio/pci: Have all VFIO PCI drivers store the vfio_pci_core_device in
drvdata
vfio/pci: Remove vfio_device_get_from_dev()
.../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 14 ++++++--
drivers/vfio/pci/mlx5/main.c | 14 ++++++--
drivers/vfio/pci/vfio_pci.c | 4 ++-
drivers/vfio/pci/vfio_pci_core.c | 36 ++++++-------------
drivers/vfio/vfio.c | 26 +-------------
include/linux/vfio.h | 2 --
include/linux/vfio_pci_core.h | 3 +-
7 files changed, 38 insertions(+), 61 deletions(-)
base-commit: 758f579843974e9603191d2d77589af98001e3b3
--
2.36.0
next reply other threads:[~2022-05-04 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 19:01 Jason Gunthorpe [this message]
2022-05-04 19:01 ` [PATCH v3 1/2] vfio/pci: Have all VFIO PCI drivers store the vfio_pci_core_device in drvdata Jason Gunthorpe
2022-05-05 18:10 ` Alex Williamson
2022-05-05 18:34 ` Jason Gunthorpe
2022-05-05 18:54 ` Alex Williamson
2022-05-05 19:28 ` Jason Gunthorpe
2022-05-04 19:01 ` [PATCH v3 2/2] vfio/pci: Remove vfio_device_get_from_dev() Jason Gunthorpe
2022-05-04 20:20 ` Kirti Wankhede
2022-05-04 21:36 ` Jason Gunthorpe
2022-05-06 21:08 ` Alex Williamson
2022-05-04 19:30 ` [PATCH v3 0/2] " Jason Gunthorpe
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=0-v3-4adf6c1b8e7c+170-vfio_get_from_dev_jgg@nvidia.com \
--to=jgg@nvidia.com \
--cc=abhsahu@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=liulongfang@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.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.