Merge tag 'drm-intel-next-2025-09-12' of...

#. All locking rules and interface contracts with cross-driver interfaces

   (dma-buf, dma_fence) need to be followed.

#. No struct_mutex anywhere in the code

#. dma_resv will be the outermost lock (when needed) and ww_acquire_ctx

   is to be hoisted at highest level and passed down within i915_gem_ctx

   in the call chain

#. While holding lru/memory manager (buddy, drm_mm, whatever) locks

   system memory allocations are not allowed

	* Enforce this by priming lockdep (with fs_reclaim). If we

	  allocate memory while holding these looks we get a rehash

	  of the shrinker vs. struct_mutex saga, and that would be

	  real bad.

#. Do not nest different lru/memory manager locks within each other.

   Take them in turn to update memory allocations, relying on the object’s

   dma_resv ww_mutex to serialize against other operations.

Level: Intermediate

Get rid of dev->struct_mutex from GEM drivers

---------------------------------------------

``dev->struct_mutex`` is the Big DRM Lock from legacy days and infested

everything. Nowadays in modern drivers the only bit where it's mandatory is

serializing GEM buffer object destruction. Which unfortunately means drivers

have to keep track of that lock and either call ``unreference`` or

``unreference_locked`` depending upon context.

Core GEM doesn't have a need for ``struct_mutex`` any more since kernel 4.8,

and there's a GEM object ``free`` callback for any drivers which are

entirely ``struct_mutex`` free.

For drivers that need ``struct_mutex`` it should be replaced with a driver-

private lock. The tricky part is the BO free functions, since those can't

reliably take that lock any more. Instead state needs to be protected with

suitable subordinate locks or some cleanup work pushed to a worker thread. For

performance-critical drivers it might also be better to go with a more

fine-grained per-buffer object and per-context lockings scheme. Currently only

the ``msm`` and `i915` drivers use ``struct_mutex``.

Contact: Simona Vetter, respective driver maintainers

Level: Advanced

Move Buffer Object Locking to dma_resv_lock()

---------------------------------------------

	mutex_destroy(&dev->master_mutex);

	mutex_destroy(&dev->clientlist_mutex);

	mutex_destroy(&dev->filelist_mutex);

	mutex_destroy(&dev->struct_mutex);

}

static int drm_dev_init(struct drm_device *dev,

	INIT_LIST_HEAD(&dev->vblank_event_list);

	spin_lock_init(&dev->event_lock);

	mutex_init(&dev->struct_mutex);

	mutex_init(&dev->filelist_mutex);

	mutex_init(&dev->clientlist_mutex);

	mutex_init(&dev->master_mutex);

	i915_scatterlist.o \

	i915_switcheroo.o \

	i915_sysfs.o \

	i915_timer_util.o \

	i915_utils.o \

	intel_clock_gating.o \

	intel_cpu_info.o \

	display/intel_modeset_setup.o \

	display/intel_modeset_verify.o \

	display/intel_overlay.o \

	display/intel_panic.o \

	display/intel_pch.o \

	display/intel_pch_display.o \

	display/intel_pch_refclk.o \

#include "i9xx_plane.h"

#include "i9xx_plane_regs.h"

#include "intel_atomic.h"

#include "intel_bo.h"

#include "intel_de.h"

#include "intel_display_irq.h"

#include "intel_display_regs.h"

#include "intel_fb.h"

#include "intel_fbc.h"

#include "intel_frontbuffer.h"

#include "intel_panic.h"

#include "intel_plane.h"

#include "intel_sprite.h"

	drm_WARN_ON(display->drm, pipe != crtc->pipe);

	intel_fb = intel_bo_alloc_framebuffer();

	intel_fb = intel_framebuffer_alloc();

	if (!intel_fb) {

		drm_dbg_kms(display->drm, "failed to alloc fb\n");

		return;