From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-xe-fixes
Date: Thu, 13 Mar 2025 12:35:37 -0400 [thread overview]
Message-ID: <Z9MJWeIlZPuvXZ_G@intel.com> (raw)
Hi Dave and Sima,
Here goes xe fixes for this week.
It is worth mention that we are disabling D3Cold on BMG because
we found some bugs where depending on the combination of BMG
card and the host, the PCI upstream port link port re-training
might fail on D3Cold -> D0 blowing things up. But while we
work with that and propagating this protection to the end
users, we are not disabling in our drm-tip to ensure that our
developers and CI can continue working with D3Cold enabled.
Everything we disable behind flags for developers will likely
be forgotten and regressions will pile up and be harder later
to re-enable it.
So, topic/xe-for-CI re-enables D3Cold. If developers ends up
having a bad combination they can workaround it by boot
parameter pcie_port_pm=off or with
echo 0 > /sys/bus/pci/devices/<bdf>/vram_d3cold_threshold
Also, the topic branch solution helps us to avoid adding the
controversial module parameters. But if there's any concern
or issues with this approach, please let me know.
Thanks,
Rodrigo.
drm-xe-fixes-2025-03-13:
- Release guc ids before cancelling work (Tejas)
- Fix new warnings around userptr (Thomas)
- Temporaritly disable D3Cold on BMG (Rodrigo)
- Retry and wait longer for GuC PC to start (Rodrigo)
- Remove redundant check in xe_vm_create_ioctl (Xin)
The following changes since commit 80e54e84911a923c40d7bee33a34c1b4be148d7a:
Linux 6.14-rc6 (2025-03-09 13:45:25 -1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-fixes-2025-03-13
for you to fetch changes up to f5d4e81774c42d9c2ea3980e570f3330ff2ed5d2:
drm/xe: remove redundant check in xe_vm_create_ioctl() (2025-03-10 14:01:43 -0400)
----------------------------------------------------------------
- Release guc ids before cancelling work (Tejas)
- Fix new warnings around userptr (Thomas)
- Temporaritly disable D3Cold on BMG (Rodrigo)
- Retry and wait longer for GuC PC to start (Rodrigo)
- Remove redundant check in xe_vm_create_ioctl (Xin)
----------------------------------------------------------------
Rodrigo Vivi (2):
drm/xe/pm: Temporarily disable D3Cold on BMG
drm/xe/guc_pc: Retry and wait longer for GuC PC start
Tejas Upadhyay (1):
drm/xe: Release guc ids before cancelling work
Thomas Hellström (1):
drm/xe/userptr: Fix an incorrect assert
Xin Wang (1):
drm/xe: remove redundant check in xe_vm_create_ioctl()
drivers/gpu/drm/xe/xe_guc_pc.c | 53 ++++++++++++++++++++++++++++----------
drivers/gpu/drm/xe/xe_guc_submit.c | 2 +-
drivers/gpu/drm/xe/xe_hmm.c | 6 ++++-
drivers/gpu/drm/xe/xe_pm.c | 13 +++++++++-
drivers/gpu/drm/xe/xe_vm.c | 3 ---
5 files changed, 58 insertions(+), 19 deletions(-)
next reply other threads:[~2025-03-13 16:35 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 16:35 Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-03 18:58 [PULL] drm-xe-fixes Rodrigo Vivi
2025-08-27 15:46 Rodrigo Vivi
2025-08-21 19:20 Rodrigo Vivi
2025-08-14 16:17 Rodrigo Vivi
2025-07-24 20:22 Thomas Hellstrom
2025-07-18 3:31 Lucas De Marchi
2025-07-11 5:17 Lucas De Marchi
2025-07-03 23:24 Lucas De Marchi
2025-06-26 14:06 Thomas Hellstrom
2025-06-19 16:03 Thomas Hellstrom
2025-06-12 16:33 Thomas Hellstrom
2025-05-23 5:47 Lucas De Marchi
2025-05-15 15:04 Lucas De Marchi
2025-05-09 5:12 Lucas De Marchi
2025-05-02 3:23 Lucas De Marchi
2025-04-18 5:43 Lucas De Marchi
2025-04-10 21:06 Lucas De Marchi
2025-03-20 18:12 Thomas Hellstrom
2025-03-06 18:01 Rodrigo Vivi
2025-02-27 16:28 Rodrigo Vivi
2025-02-20 16:54 Rodrigo Vivi
2025-02-13 17:25 Rodrigo Vivi
2025-02-06 13:48 Rodrigo Vivi
2025-01-16 20:02 Thomas Hellstrom
2025-01-09 18:59 Thomas Hellstrom
2025-01-02 19:53 Thomas Hellstrom
2024-12-23 17:53 Thomas Hellstrom
2025-01-02 19:55 ` Thomas Hellström
2024-12-12 19:28 Thomas Hellstrom
2024-12-04 14:08 Thomas Hellstrom
2024-11-15 0:03 Lucas De Marchi
2024-11-08 15:28 Lucas De Marchi
2024-11-01 10:41 Lucas De Marchi
2024-10-24 23:15 Lucas De Marchi
2024-10-18 3:33 Lucas De Marchi
2024-10-11 3:12 Lucas De Marchi
2024-10-03 14:15 Lucas De Marchi
2024-09-12 14:46 Rodrigo Vivi
2024-09-05 13:28 Rodrigo Vivi
2024-08-29 13:59 Rodrigo Vivi
2024-08-22 15:12 Rodrigo Vivi
2024-08-15 14:02 Rodrigo Vivi
2024-08-08 17:55 Rodrigo Vivi
2024-07-11 22:16 Lucas De Marchi
2024-07-04 10:51 Thomas Hellstrom
2024-07-04 14:46 ` Daniel Vetter
2024-06-20 8:02 Thomas Hellstrom
2024-06-13 11:26 Thomas Hellstrom
2024-06-04 15:09 Thomas Hellstrom
2024-05-30 16:41 Thomas Hellstrom
2024-05-09 19:26 Lucas De Marchi
2024-05-02 16:37 Lucas De Marchi
2024-04-25 20:50 Lucas De Marchi
2024-04-18 15:47 Lucas De Marchi
2024-04-11 17:34 Lucas De Marchi
2024-04-04 14:49 Lucas De Marchi
2024-03-26 17:10 Lucas De Marchi
2024-03-07 10:48 Thomas Hellstrom
2024-02-29 13:07 Thomas Hellstrom
2024-02-22 11:12 Thomas Hellstrom
2024-02-15 12:43 Thomas Hellstrom
2024-02-08 11:08 Thomas Hellstrom
2024-02-01 11:37 Thomas Hellstrom
2024-02-01 11:42 ` Thomas Hellström
2024-01-25 8:29 Thomas Hellstrom
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=Z9MJWeIlZPuvXZ_G@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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).