Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, Jocelyn Falempe <jfalempe@redhat.com>
Subject: [PATCH 0/6] drm/{i915, xe}/panic: drop dependency on struct intel_framebuffer
Date: Tue,  2 Jun 2026 13:09:03 +0300	[thread overview]
Message-ID: <cover.1780394867.git.jani.nikula@intel.com> (raw)

Having i915 and xe panic code depend on struct intel_framebuffer is a
bit annoying. Break that dependency by storing the tiling function
pointer in struct intel_panic, and storing intel_panic pointer in struct
drm_scanout_buffer .private member. Do a bunch of cleanups first to make
it easier.


Cc: Jocelyn Falempe <jfalempe@redhat.com>

Jani Nikula (6):
  drm/i915/panic: split out i915_gem_panic.[ch]
  drm/i915/panic: squash i915_panic.c into i915_gem_panic.c
  drm/i915/panic: remove the extra layer from panic hooks
  drm/{i915,xe}/panic: pass obj to panic setup
  drm/xe/panic: store fb bo in struct intel_panic
  drm/{i915,xe}/panic: drop dependency on struct intel_framebuffer

 drivers/gpu/drm/i915/Makefile                 |   4 +-
 .../drm/i915/display/intel_display_types.h    |   1 -
 drivers/gpu/drm/i915/display/intel_parent.c   |   6 +-
 drivers/gpu/drm/i915/display/intel_parent.h   |   4 +-
 drivers/gpu/drm/i915/display/intel_plane.c    |   8 +-
 drivers/gpu/drm/i915/gem/i915_gem_object.h    |   7 -
 drivers/gpu/drm/i915/gem/i915_gem_pages.c     | 128 ---------------
 drivers/gpu/drm/i915/gem/i915_gem_panic.c     | 147 ++++++++++++++++++
 drivers/gpu/drm/i915/gem/i915_gem_panic.h     |  11 ++
 drivers/gpu/drm/i915/i915_driver.c            |   2 +-
 drivers/gpu/drm/i915/i915_panic.c             |  35 -----
 drivers/gpu/drm/i915/i915_panic.h             |   9 --
 drivers/gpu/drm/xe/display/xe_panic.c         |  26 ++--
 include/drm/intel/display_parent_interface.h  |   4 +-
 14 files changed, 191 insertions(+), 201 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/gem/i915_gem_panic.c
 create mode 100644 drivers/gpu/drm/i915/gem/i915_gem_panic.h
 delete mode 100644 drivers/gpu/drm/i915/i915_panic.c
 delete mode 100644 drivers/gpu/drm/i915/i915_panic.h

-- 
2.47.3


             reply	other threads:[~2026-06-02 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 10:09 Jani Nikula [this message]
2026-06-02 10:09 ` [PATCH 1/6] drm/i915/panic: split out i915_gem_panic.[ch] Jani Nikula
2026-06-02 10:09 ` [PATCH 2/6] drm/i915/panic: squash i915_panic.c into i915_gem_panic.c Jani Nikula
2026-06-02 10:09 ` [PATCH 3/6] drm/i915/panic: remove the extra layer from panic hooks Jani Nikula
2026-06-02 10:09 ` [PATCH 4/6] drm/{i915,xe}/panic: pass obj to panic setup Jani Nikula
2026-06-02 10:09 ` [PATCH 5/6] drm/xe/panic: store fb bo in struct intel_panic Jani Nikula
2026-06-02 10:09 ` [PATCH 6/6] drm/{i915, xe}/panic: drop dependency on struct intel_framebuffer Jani Nikula
2026-06-02 10:15 ` ✗ CI.checkpatch: warning for " Patchwork
2026-06-02 10:17 ` ✓ CI.KUnit: success " Patchwork
2026-06-02 11:02 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-02 18:29 ` ✓ Xe.CI.FULL: " 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=cover.1780394867.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jfalempe@redhat.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