From: Raag Jadav <raag.jadav@intel.com>
To: Maarten Lankhorst <maarten@lankhorst.se>
Cc: intel-xe@lists.freedesktop.org, matthew.brost@intel.com,
rodrigo.vivi@intel.com, thomas.hellstrom@linux.intel.com,
riana.tauro@intel.com, michal.wajdeczko@intel.com,
matthew.d.roper@intel.com, michal.winiarski@intel.com
Subject: Re: [PATCH v1 6/6] drm/xe/pci: Introduce PCIe FLR
Date: Thu, 26 Feb 2026 17:46:31 +0100 [thread overview]
Message-ID: <aaB450NUrl3kl6eW@black.igk.intel.com> (raw)
In-Reply-To: <38ac79bb-0d22-4f3f-b80b-9763aeb227eb@lankhorst.se>
On Thu, Feb 26, 2026 at 05:42:05PM +0100, Maarten Lankhorst wrote:
> Den 2026-02-24 kl. 11:25, skrev Raag Jadav:
> > With all the pieces in place, we can finally introduce PCIe FLR handling
> > which reloads hardware state without the need for reloading the driver
> > from userspace. Memory contents are also wiped along with hardware state,
> > so user still needs to recreate buffers and reload context after FLR.
> >
> This probably needs some more help to support display.
> I tried using only FLR to tear down the driver during shutdown,
> but that ran into some issues unfortunately and was reverted.
Yes, it's missing migrate and lrc pieces. Hold on for v2.
Raag
next prev parent reply other threads:[~2026-02-26 16:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 10:25 [PATCH v1 0/6] Introduce Xe PCIe FLR Raag Jadav
2026-02-24 10:25 ` [PATCH v1 1/6] drm/xe/uc_fw: Allow reloading firmware Raag Jadav
2026-02-24 10:25 ` [PATCH v1 2/6] drm/xe/uc: Introduce FLR helpers Raag Jadav
2026-02-24 10:25 ` [PATCH v1 3/6] drm/xe/irq: Introduce FLR helper Raag Jadav
2026-02-24 10:25 ` [PATCH v1 4/6] drm/xe: Introduce xe_device_assert_lmem_ready() Raag Jadav
2026-02-24 10:25 ` [PATCH v1 5/6] drm/xe/bo_evict: Introduce xe_bo_restore_map() Raag Jadav
2026-02-24 22:11 ` Matthew Brost
2026-02-26 12:13 ` Raag Jadav
2026-02-24 10:25 ` [PATCH v1 6/6] drm/xe/pci: Introduce PCIe FLR Raag Jadav
2026-02-26 16:42 ` Maarten Lankhorst
2026-02-26 16:46 ` Raag Jadav [this message]
2026-02-26 16:55 ` Raag Jadav
2026-02-24 10:36 ` ✗ CI.checkpatch: warning for Introduce Xe " Patchwork
2026-02-24 10:38 ` ✓ CI.KUnit: success " Patchwork
2026-02-26 10:28 ` [PATCH v1 0/6] " Jani Nikula
2026-02-26 12:31 ` Raag Jadav
2026-02-26 16:08 ` Matthew Auld
2026-02-26 16:37 ` Raag Jadav
2026-02-26 22:12 ` Matt Roper
2026-02-27 4:18 ` Raag Jadav
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=aaB450NUrl3kl6eW@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten@lankhorst.se \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@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 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.