Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jocelyn Falempe <jfalempe@redhat.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: Jocelyn Falempe <jfalempe@redhat.com>
Subject: [PATCH v3 0/2] drm/xe/display: Make panic support work on vram.
Date: Thu, 16 Oct 2025 09:52:29 +0200	[thread overview]
Message-ID: <20251016075701.379023-1-jfalempe@redhat.com> (raw)

With panic support merged, enable on vram too.
I've only rebased the v2 on top of intel-drm-next.

v2:
- Add kerneldoc to xe_bo_is_visible_vram,
- reduce amount of members in xe_panic_data to minimum.

v3:
- Rebase, and take care of the code moved from intel_bo.c to
  xe_panic.c

Maarten Lankhorst (2):
  drm/xe: Extract xe_bo_is_visible_vram
  drm/xe/display: Make panic support work on vram.

 drivers/gpu/drm/xe/display/xe_panic.c | 50 +++++++++++++++++++--------
 drivers/gpu/drm/xe/xe_bo.c            | 19 +++++++++-
 drivers/gpu/drm/xe/xe_bo.h            |  1 +
 3 files changed, 55 insertions(+), 15 deletions(-)


base-commit: 56d9d03450f065fd31e56de5fafa7d498b318531
-- 
2.51.0


             reply	other threads:[~2025-10-16  7:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16  7:52 Jocelyn Falempe [this message]
2025-10-16  7:52 ` [PATCH v3 1/2] drm/xe: Extract xe_bo_is_visible_vram Jocelyn Falempe
2025-10-16  7:52 ` [PATCH v3 2/2] drm/xe/display: Make panic support work on vram Jocelyn Falempe
2025-10-17 15:35   ` Maarten Lankhorst
2025-10-17 22:18     ` Jocelyn Falempe
2025-10-21 11:51       ` Maarten Lankhorst
2025-10-16  8:04 ` ✓ CI.KUnit: success for drm/xe/display: Make panic support work on vram. (rev3) Patchwork
2025-10-16  8:48 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-17  2:45 ` ✗ Xe.CI.Full: failure " Patchwork

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=20251016075701.379023-1-jfalempe@redhat.com \
    --to=jfalempe@redhat.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=maarten.lankhorst@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