From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Matthew Auld" <matthew.auld@intel.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: [PATCH 0/2] drm/ttm: Improve the TTM operation context gfp_retry_mayfail behaviour
Date: Fri, 27 Feb 2026 17:00:10 +0100 [thread overview]
Message-ID: <20260227160012.82309-1-thomas.hellstrom@linux.intel.com> (raw)
Two small patches around the gfp_retry_mayfail behaviour:
Patch 1 ensures we don't spam the kernel log on allocation failures.
Patch 2 extends the gfp_retry_mayfail to swap readback.
Thomas Hellström (2):
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
drivers/gpu/drm/ttm/ttm_backup.c | 6 ++++--
drivers/gpu/drm/ttm/ttm_pool.c | 7 +++++--
include/drm/ttm/ttm_backup.h | 2 +-
3 files changed, 10 insertions(+), 5 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-27 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 16:00 Thomas Hellström [this message]
2026-02-27 16:00 ` [PATCH 1/2] drm/ttm: Don't spam the log on buffer object backing store allocation failure Thomas Hellström
2026-02-27 21:01 ` Matthew Brost
2026-03-02 9:02 ` Christian König
2026-03-02 9:39 ` Thomas Hellström
2026-03-09 9:36 ` Simona Vetter
2026-02-27 16:00 ` [PATCH 2/2] drm/ttm: Avoid invoking the OOM killer when reading back swapped content Thomas Hellström
2026-03-10 14:10 ` Maarten Lankhorst
2026-02-27 17:06 ` ✓ CI.KUnit: success for drm/ttm: Improve the TTM operation context gfp_retry_mayfail behaviour Patchwork
2026-02-27 17:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-28 3:48 ` ✗ 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=20260227160012.82309-1-thomas.hellstrom@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