public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Laguna, Lukasz" <lukasz.laguna@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Jadav, Raag" <raag.jadav@intel.com>,
	"aravind.iddamsetty@linux.intel.com"
	<aravind.iddamsetty@linux.intel.com>
Cc: "Auld, Matthew" <matthew.auld@intel.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>,
	"Brost, Matthew" <matthew.brost@intel.com>,
	"Winiarski, Michal" <michal.winiarski@intel.com>,
	"thomas.hellstrom@linux.intel.com"
	<thomas.hellstrom@linux.intel.com>,
	"maarten@lankhorst.se" <maarten@lankhorst.se>,
	"Tauro, Riana" <riana.tauro@intel.com>,
	"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>
Subject: Re: [PATCH v2 9/9] drm/xe/pci: Introduce PCIe FLR
Date: Mon, 2 Mar 2026 20:37:11 +0100	[thread overview]
Message-ID: <ae00396c-e643-4044-a06f-724498c1fabe@intel.com> (raw)
In-Reply-To: <f6183892f5caac00192c83b213e3e22e5e9ad453.camel@intel.com>


On 2/27/2026 18:49, Vivi, Rodrigo wrote:
> On Fri, 2026-02-27 at 22:30 +0530, Raag Jadav wrote:
>> With all the pieces in place, we can finally introduce PCIe Function
>> Level
>> Reset (FLR) handling which re-initializes hardware state without the
>> need
>> for reloading the driver from userspace. All VRAM contents are lost
>> along
>> with hardware state, so the driver takes care of recreating the
>> required
>> kernel bos as part of re-initialization, but user still needs to
>> recreate
>> user bos and reload context after PCIe FLR.
>>
>> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
>
> Do we really have everything in place? I'm missing the handling of VF
> here. Hence we would have the same deadlock pointed out by Michal when
> Aravind attempted it last time, no?!

This seems to be different from Aravind's previous attempt. Here we 
don't remove the driver and as a result we won't attempt to disable VFs, 
so the deadlock scenario shouldn't apply.

Lukasz

> We probably need to use the guc relay communication here so PF can
> inform VF of the FLR, then stop all the workload and wedge the device,
> before the AER triggers a kill of the VM, no?!
>
>> ---
>> v2: Spell out Function Level Reset (Jani)
>> ---
>>   drivers/gpu/drm/xe/Makefile     |   1 +
>>   drivers/gpu/drm/xe/xe_pci.c     |   1 +
>>   drivers/gpu/drm/xe/xe_pci.h     |   2 +
>>   drivers/gpu/drm/xe/xe_pci_err.c | 150
>> ++++++++++++++++++++++++++++++++
>>   4 files changed, 154 insertions(+)
>>   create mode 100644 drivers/gpu/drm/xe/xe_pci_err.c
>>
>> diff --git a/drivers/gpu/drm/xe/Makefile
>> b/drivers/gpu/drm/xe/Makefile
>> index 7fc67c320086..bc468a9afc48 100644
>> --- a/drivers/gpu/drm/xe/Makefile
>> +++ b/drivers/gpu/drm/xe/Makefile
>> @@ -99,6 +99,7 @@ xe-y += xe_bb.o \
>>   	xe_page_reclaim.o \
>>   	xe_pat.o \
>>   	xe_pci.o \
>> +	xe_pci_err.o \
>>   	xe_pci_rebar.o \
>>   	xe_pcode.o \
>>   	xe_pm.o \
>> diff --git a/drivers/gpu/drm/xe/xe_pci.c
>> b/drivers/gpu/drm/xe/xe_pci.c
>> index 0a3bc5067a76..47a2f9de9d61 100644
>> --- a/drivers/gpu/drm/xe/xe_pci.c
>> +++ b/drivers/gpu/drm/xe/xe_pci.c
>> @@ -1301,6 +1301,7 @@ static struct pci_driver xe_pci_driver = {
>>   #ifdef CONFIG_PM_SLEEP
>>   	.driver.pm = &xe_pm_ops,
>>   #endif
>> +	.err_handler = &xe_pci_err_handlers,
>>   };
>>   
>>   /**
>> diff --git a/drivers/gpu/drm/xe/xe_pci.h
>> b/drivers/gpu/drm/xe/xe_pci.h
>> index 11bcc5fe2c5b..85e85e8508c3 100644
>> --- a/drivers/gpu/drm/xe/xe_pci.h
>> +++ b/drivers/gpu/drm/xe/xe_pci.h
>> @@ -8,6 +8,8 @@
>>   
>>   struct pci_dev;
>>   
>> +extern const struct pci_error_handlers xe_pci_err_handlers;
>> +
>>   int xe_register_pci_driver(void);
>>   void xe_unregister_pci_driver(void);
>>   struct xe_device *xe_pci_to_pf_device(struct pci_dev *pdev);
>> diff --git a/drivers/gpu/drm/xe/xe_pci_err.c
>> b/drivers/gpu/drm/xe/xe_pci_err.c
>> new file mode 100644
>> index 000000000000..16fc6a9f8289
>> --- /dev/null
>> +++ b/drivers/gpu/drm/xe/xe_pci_err.c
>> @@ -0,0 +1,150 @@
>> +// SPDX-License-Identifier: MIT
>> +/*
>> + * Copyright © 2026 Intel Corporation
>> + */
>> +
>> +#include "xe_bo_evict.h"
>> +#include "xe_device.h"
>> +#include "xe_gt.h"
>> +#include "xe_gt_idle.h"
>> +#include "xe_i2c.h"
>> +#include "xe_irq.h"
>> +#include "xe_late_bind_fw.h"
>> +#include "xe_pci.h"
>> +#include "xe_pcode.h"
>> +#include "xe_printk.h"
>> +#include "xe_pxp.h"
>> +#include "xe_wa.h"
>> +
>> +static int xe_flr_prepare(struct xe_device *xe)
>> +{
>> +	struct xe_gt *gt;
>> +	int err;
>> +	u8 id;
>> +
>> +	err = xe_pxp_pm_suspend(xe->pxp);
>> +	if (err)
>> +		return err;
>> +
>> +	xe_late_bind_wait_for_worker_completion(&xe->late_bind);
>> +
>> +	for_each_gt(gt, xe, id)
>> +		xe_gt_flr_prepare(gt);
>> +
>> +	xe_irq_disable(xe);
>> +
>> +	// TODO: Drop all user bos
>> +	xe_bo_pci_dev_remove_pinned(xe);
>> +
>> +	return 0;
>> +}
>> +
>> +static int xe_flr_done(struct xe_device *xe)
>> +{
>> +	struct xe_tile *tile;
>> +	struct xe_gt *gt;
>> +	int err;
>> +	u8 id;
>> +
>> +	for_each_gt(gt, xe, id)
>> +		xe_gt_idle_disable_c6(gt);
>> +
>> +	for_each_tile(tile, xe, id)
>> +		xe_wa_apply_tile_workarounds(tile);
>> +
>> +	err = xe_pcode_ready(xe, true);
>> +	if (err)
>> +		return err;
>> +
>> +	xe_device_assert_lmem_ready(xe);
>> +
>> +	err = xe_bo_restore_map(xe);
>> +	if (err)
>> +		return err;
>> +
>> +	for_each_gt(gt, xe, id) {
>> +		err = xe_gt_flr_done(gt);
>> +		if (err)
>> +			return err;
>> +	}
>> +
>> +	xe_i2c_pm_resume(xe, true);
>> +
>> +	xe_irq_resume(xe);
>> +
>> +	for_each_gt(gt, xe, id) {
>> +		err = xe_gt_resume(gt);
>> +		if (err)
>> +			return err;
>> +	}
>> +
>> +	xe_pxp_pm_resume(xe->pxp);
>> +
>> +	xe_late_bind_fw_load(&xe->late_bind);
>> +
>> +	return 0;
>> +}
>> +
>> +static void xe_pci_reset_prepare(struct pci_dev *pdev)
>> +{
>> +	struct xe_device *xe = pdev_to_xe_device(pdev);
>> +
>> +	/* TODO: Extend support as a follow-up */
>> +	if (!IS_DGFX(xe) || IS_SRIOV_VF(xe) || pci_num_vf(pdev) ||
>> xe->info.probe_display) {
>> +		xe_err(xe, "PCIe FLR not supported\n");
>> +		return;
>> +	}
>> +
>> +	/* Wedge the device to prevent userspace access but don't
>> send the event yet */
>> +	atomic_set(&xe->wedged.flag, 1);
>> +
>> +	/*
>> +	 * The hardware could be in corrupted state and access
>> unreliable, but we try to
>> +	 * update data structures and cleanup any pending work to
>> avoid side effects during
>> +	 * PCIe FLR. This will be similar to xe_pm_suspend() flow
>> but without migration.
>> +	 */
>> +	if (xe_flr_prepare(xe)) {
>> +		xe_err(xe, "Failed to prepare for PCIe FLR\n");
>> +		return;
>> +	}
>> +
>> +	xe_info(xe, "Prepared for PCIe FLR\n");
>> +}
>> +
>> +static void xe_pci_reset_done(struct pci_dev *pdev)
>> +{
>> +	struct xe_device *xe = pdev_to_xe_device(pdev);
>> +
>> +	/* TODO: Extend support as a follow-up */
>> +	if (!IS_DGFX(xe) || IS_SRIOV_VF(xe) || pci_num_vf(pdev) ||
>> xe->info.probe_display)
>> +		return;
>> +
>> +	if (!xe_device_wedged(xe)) {
>> +		xe_err(xe, "Device in unexpected state, re-
>> initialization aborted\n");
>> +		return;
>> +	}
>> +
>> +	/*
>> +	 * We already have the data structures intact, so try to re-
>> initialize the device.
>> +	 * This will be similar to xe_pm_resume() flow, except we'll
>> also need to recreate
>> +	 * all VRAM contents.
>> +	 */
>> +	if (xe_flr_done(xe)) {
>> +		xe_err(xe, "Re-initialization failed\n");
>> +		return;
>> +	}
>> +
>> +	/* Unwedge to allow userspace access */
>> +	atomic_set(&xe->wedged.flag, 0);
>> +
>> +	xe_info(xe, "Re-initialization success\n");
>> +}
>> +
>> +/*
>> + * PCIe Function Level Reset (FLR) support only.
>> + * TODO: Add PCIe error handlers using similar flow.
>> + */
>> +const struct pci_error_handlers xe_pci_err_handlers = {
>> +	.reset_prepare = xe_pci_reset_prepare,
>> +	.reset_done = xe_pci_reset_done,
>> +};

  parent reply	other threads:[~2026-03-02 19:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 17:00 [PATCH v2 0/9] Introduce Xe PCIe FLR Raag Jadav
2026-02-27 17:00 ` [PATCH v2 1/9] drm/xe/uc_fw: Allow re-initializing firmware Raag Jadav
2026-02-27 17:00 ` [PATCH v2 2/9] drm/xe/gt: Introduce FLR helpers Raag Jadav
2026-02-27 17:00 ` [PATCH v2 3/9] drm/xe/irq: Introduce xe_irq_disable() Raag Jadav
2026-02-27 17:00 ` [PATCH v2 4/9] drm/xe: Introduce xe_device_assert_lmem_ready() Raag Jadav
2026-02-27 17:00 ` [PATCH v2 5/9] drm/xe/bo_evict: Introduce xe_bo_restore_map() Raag Jadav
2026-02-27 17:00 ` [PATCH v2 6/9] drm/xe/lrc: Introduce xe_lrc_reinit() Raag Jadav
2026-02-27 18:06   ` Matthew Brost
2026-02-28  5:11     ` Raag Jadav
2026-02-27 17:00 ` [PATCH v2 7/9] drm/xe/exec_queue: Introduce xe_exec_queue_reinit() Raag Jadav
2026-02-27 17:00 ` [PATCH v2 8/9] drm/xe/migrate: Introduce xe_migrate_reinit() Raag Jadav
2026-02-27 18:32   ` Matthew Brost
2026-02-28  5:12     ` Raag Jadav
2026-03-03  5:29       ` Raag Jadav
2026-02-27 17:00 ` [PATCH v2 9/9] drm/xe/pci: Introduce PCIe FLR Raag Jadav
2026-02-27 17:49   ` Vivi, Rodrigo
2026-02-28  5:24     ` Raag Jadav
2026-03-02 16:58       ` Rodrigo Vivi
2026-03-02 19:37     ` Laguna, Lukasz [this message]
2026-02-27 17:50 ` [PATCH v2 0/9] Introduce Xe " Vivi, Rodrigo

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=ae00396c-e643-4044-a06f-724498c1fabe@intel.com \
    --to=lukasz.laguna@intel.com \
    --cc=Michal.Wajdeczko@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten@lankhorst.se \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.intel.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