All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thomas.hellstrom@linux.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-next-fixes for 6.19
Date: Thu, 4 Dec 2025 23:09:12 +0100	[thread overview]
Message-ID: <aTIGiHJnnMtqbDOO@fedora> (raw)

Hi Dave, Simona
A last drm-xe-next-fixes for 6.19 with fixes that would be good to have
in -rc1.

Thanks,
Thomas

drm-xe-next-fixes-2025-12-04:

Driver Changes:
- Fix a memory leak (Mika)
- Fix a 64-bit division (Michal Wajdeczko)
- vf migration fix (Matt Brost)
- LRC pause Fix (Tomasz lis)
The following changes since commit 0692602defb0c273f80dec9c564ca50726404aca:

  Merge tag 'amd-drm-next-6.19-2025-12-02' of https://gitlab.freedesktop.org/agd5f/linux into drm-next (2025-12-03 09:43:49 +1000)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2025-12-04

for you to fetch changes up to 3f1c07fc21c68bd3bd2df9d2c9441f6485e934d9:

  Merge drm/drm-next into drm-xe-next-fixes (2025-12-04 22:54:56 +0100)

----------------------------------------------------------------
Driver Changes:
- Fix a memory leak (Mika)
- Fix a 64-bit division (Michal Wajdeczko)
- vf migration fix (Matt Brost)
- LRC pause Fix (Tomasz lis)

----------------------------------------------------------------
Matthew Brost (1):
      drm/xe/vf: Start re-emission from first unsignaled job during VF migration

Michal Wajdeczko (1):
      drm/xe/pf: Use div_u64 when calculating GGTT profile

Mika Kuoppala (1):
      drm/xe: Fix memory leak when handling pagefault vma

Thomas Hellström (1):
      Merge drm/drm-next into drm-xe-next-fixes

Tomasz Lis (1):
      drm/xe: Protect against unset LRC when pausing submissions

 drivers/gpu/drm/xe/xe_gpu_scheduler.h      |  5 ++--
 drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c |  2 +-
 drivers/gpu/drm/xe/xe_guc_submit.c         | 47 +++++++++++++++++++-----------
 drivers/gpu/drm/xe/xe_pagefault.c          |  1 -
 drivers/gpu/drm/xe/xe_sched_job_types.h    |  4 +--
 5 files changed, 36 insertions(+), 23 deletions(-)

                 reply	other threads:[~2025-12-04 22:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aTIGiHJnnMtqbDOO@fedora \
    --to=thomas.hellstrom@linux.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=rodrigo.vivi@intel.com \
    --cc=simona.vetter@ffwll.ch \
    --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 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.