From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
"Alex Williamson" <alex@shazbot.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Yishai Hadas" <yishaih@nvidia.com>,
"Kevin Tian" <kevin.tian@intel.com>,
"Shameer Kolothum" <skolothumtho@nvidia.com>,
intel-xe@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, "Matthew Brost" <matthew.brost@intel.com>
Cc: <dri-devel@lists.freedesktop.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
"Lukasz Laguna" <lukasz.laguna@intel.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v5 25/28] drm/xe/pci: Introduce a helper to allow VF access to PF xe_device
Date: Sat, 22 Nov 2025 19:38:38 +0100 [thread overview]
Message-ID: <582e26ce-4579-4c90-9fab-40f705e89cc9@intel.com> (raw)
In-Reply-To: <20251111010439.347045-26-michal.winiarski@intel.com>
On 11/11/2025 2:04 AM, Michał Winiarski wrote:
> In certain scenarios (such as VF migration), VF driver needs to interact
> with PF driver.
> Add a helper to allow VF driver access to PF xe_device.
>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pci.c | 17 +++++++++++++++++
> drivers/gpu/drm/xe/xe_pci.h | 3 +++
> 2 files changed, 20 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index cd03b4b3ebdbd..5107a21679503 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -1224,6 +1224,23 @@ static struct pci_driver xe_pci_driver = {
> #endif
> };
>
> +/**
> + * xe_pci_get_pf() - Get PF &xe_device.
nit: xe_pci_to_pf_device() ?
as "get" is usually used in simple 'getter' functions
while here we perform extra checks
> + * @pdev: the VF &pci_dev device
> + *
> + * Return: pointer to PF &xe_device, NULL otherwise.
> + */
> +struct xe_device *xe_pci_get_pf(struct pci_dev *pdev)
> +{
> + struct drm_device *drm;
> +
> + drm = pci_iov_get_pf_drvdata(pdev, &xe_pci_driver);
> + if (IS_ERR(drm))
> + return NULL;
> +
> + return to_xe_device(drm);
> +}
> +
> int xe_register_pci_driver(void)
> {
> return pci_register_driver(&xe_pci_driver);
> diff --git a/drivers/gpu/drm/xe/xe_pci.h b/drivers/gpu/drm/xe/xe_pci.h
> index 611c1209b14cc..e97800d5c9dc3 100644
> --- a/drivers/gpu/drm/xe/xe_pci.h
> +++ b/drivers/gpu/drm/xe/xe_pci.h
> @@ -6,6 +6,9 @@
> #ifndef _XE_PCI_H_
> #define _XE_PCI_H_
>
> +struct pci_dev;
> +
> +struct xe_device *xe_pci_get_pf(struct pci_dev *pdev);
nit: since this is just a helper, move its declaration below core
functions register/unregister
> int xe_register_pci_driver(void);
> void xe_unregister_pci_driver(void);
>
just nits, so
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
next prev parent reply other threads:[~2025-11-22 18:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 1:04 [PATCH v5 00/28] vfio/xe: Add driver variant for Xe VF migration Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 01/28] drm/xe/pf: Remove GuC version check for migration support Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 02/28] drm/xe: Move migration support to device-level struct Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 03/28] drm/xe/pf: Convert control state to bitmap Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 04/28] drm/xe/pf: Add save/restore control state stubs and connect to debugfs Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 05/28] drm/xe/pf: Add data structures and handlers for migration rings Michał Winiarski
2025-11-11 18:35 ` Michal Wajdeczko
2025-11-12 12:12 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 06/28] drm/xe/pf: Add helpers for migration data packet allocation / free Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 07/28] drm/xe/pf: Add support for encap/decap of bitstream to/from packet Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 08/28] drm/xe/pf: Add minimalistic migration descriptor Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 09/28] drm/xe/pf: Expose VF migration data size over debugfs Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 10/28] drm/xe: Add sa/guc_buf_cache sync interface Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 11/28] drm/xe: Allow the caller to pass guc_buf_cache size Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 12/28] drm/xe/pf: Increase PF GuC Buffer Cache size and use it for VF migration Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 13/28] drm/xe/pf: Remove GuC migration data save/restore from GT debugfs Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 14/28] drm/xe/pf: Don't save GuC VF migration data on pause Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 15/28] drm/xe/pf: Switch VF migration GuC save/restore to struct migration data Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 16/28] drm/xe/pf: Handle GuC migration data as part of PF control Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 17/28] drm/xe/pf: Add helpers for VF GGTT migration data handling Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 18/28] drm/xe/pf: Handle GGTT migration data as part of PF control Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 19/28] drm/xe/pf: Handle MMIO " Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 20/28] drm/xe/pf: Add helper to retrieve VF's LMEM object Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 21/28] drm/xe/migrate: Add function to copy of VRAM data in chunks Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 22/28] drm/xe/pf: Handle VRAM migration data as part of PF control Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 23/28] drm/xe/pf: Add wait helper for VF FLR Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 24/28] drm/xe/pf: Enable SR-IOV VF migration Michał Winiarski
2025-11-17 18:48 ` Alex Williamson
2025-11-20 9:48 ` Michał Winiarski
2025-11-22 18:10 ` Michal Wajdeczko
2025-11-24 21:19 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 25/28] drm/xe/pci: Introduce a helper to allow VF access to PF xe_device Michał Winiarski
2025-11-22 18:38 ` Michal Wajdeczko [this message]
2025-11-24 21:17 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 26/28] drm/xe/pf: Export helpers for VFIO Michał Winiarski
2025-11-22 17:45 ` Michal Wajdeczko
2025-11-24 21:25 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 27/28] drm/intel/bmg: Allow device ID usage with single-argument macros Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 28/28] vfio/xe: Add device specific vfio_pci driver variant for Intel graphics Michał Winiarski
2025-11-11 1:38 ` Tian, Kevin
2025-11-11 8:25 ` Winiarski, Michal
2025-11-11 9:53 ` Tian, Kevin
2025-11-12 13:46 ` Winiarski, Michal
2025-11-17 17:41 ` Jason Gunthorpe
2025-11-20 12:40 ` Winiarski, Michal
2025-11-21 7:19 ` Tian, Kevin
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=582e26ce-4579-4c90-9fab-40f705e89cc9@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=airlied@gmail.com \
--cc=alex@shazbot.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=lukasz.laguna@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.winiarski@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=skolothumtho@nvidia.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox