public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org,
	"Christian König" <christian.koenig@amd.com>
Cc: Matthew Brost <matthew.brost@intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/3] drm/ttm: Improve the TTM operation context gfp_retry_mayfail behaviour
Date: Thu, 19 Mar 2026 20:30:43 +0100	[thread overview]
Message-ID: <237c24790679ebf668bf1d38155ac8888d211028.camel@linux.intel.com> (raw)
In-Reply-To: <dbb22727c88887375737f5a837b245ca22bed988.camel@linux.intel.com>

Hi!

Since Sima was OK with this series and I believe the changes are
completely non-controversial, I'll go ahead and merge this tomorrow
through drm-misc-next.

Thanks,
Thomas


On Wed, 2026-03-18 at 15:50 +0100, Thomas Hellström wrote:
> @Christian, Ack to merge these?
> 
> Thanks,
> Thomas
> 
> 
> On Tue, 2026-03-17 at 15:18 +0100, Thomas Hellström wrote:
> > Two small patches around the gfp_retry_mayfail behaviour, and
> > one patch to improve associated kerneldoc.
> > 
> > Patch 1 ensures we don't spam the kernel log on allocation
> > failures.
> > 
> > Patch 2 extends the gfp_retry_mayfail to swap readback.
> > 
> > Patch 3 Improves on the associated kerneldocs.
> > 
> > v2:
> > - Add patch 3. (Sima).
> > 
> > Thomas Hellström (3):
> >   drm/ttm: Don't spam the log on buffer object backing store
> > allocation
> >     failure
> >   drm/ttm: Avoid invoking the OOM killer when reading back swapped
> >     content
> >   drm/ttm: Update the struct ttm_operation_ctx kerneldoc
> > 
> >  drivers/gpu/drm/ttm/ttm_backup.c |  6 ++++--
> >  drivers/gpu/drm/ttm/ttm_pool.c   |  7 +++++--
> >  include/drm/ttm/ttm_backup.h     |  2 +-
> >  include/drm/ttm/ttm_bo.h         | 28 +++++++++++++++++++---------
> >  4 files changed, 29 insertions(+), 14 deletions(-)

  reply	other threads:[~2026-03-19 19:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 14:18 [PATCH v2 0/3] drm/ttm: Improve the TTM operation context gfp_retry_mayfail behaviour Thomas Hellström
2026-03-17 14:18 ` [PATCH v2 1/3] drm/ttm: Don't spam the log on buffer object backing store allocation failure Thomas Hellström
2026-03-17 14:18 ` [PATCH v2 2/3] drm/ttm: Avoid invoking the OOM killer when reading back swapped content Thomas Hellström
2026-03-17 14:18 ` [PATCH v2 3/3] drm/ttm: Update the struct ttm_operation_ctx kerneldoc Thomas Hellström
2026-03-18 11:48   ` Maarten Lankhorst
2026-03-17 14:42 ` ✓ CI.KUnit: success for drm/ttm: Improve the TTM operation context gfp_retry_mayfail behaviour (rev2) Patchwork
2026-03-17 15:18 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-18 14:50 ` [PATCH v2 0/3] drm/ttm: Improve the TTM operation context gfp_retry_mayfail behaviour Thomas Hellström
2026-03-19 19:30   ` Thomas Hellström [this message]
2026-03-20  8:42     ` Christian König
2026-03-20  8:43       ` Thomas Hellström
2026-03-19  0:24 ` ✓ Xe.CI.FULL: success for drm/ttm: Improve the TTM operation context gfp_retry_mayfail behaviour (rev2) 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=237c24790679ebf668bf1d38155ac8888d211028.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@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