From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: thomas.hellstrom@linux.intel.com,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
nouveau@lists.freedesktop.org
Subject: Rework TTMs busy handling
Date: Fri, 26 Jan 2024 15:09:14 +0100 [thread overview]
Message-ID: <20240126140916.1577-1-christian.koenig@amd.com> (raw)
Hi guys,
so pushed the first few patches from this series. I hope that I
correctly managed to resolve the silent Xe merge conflict in drm-tip,
but would be nice if somebody could double check.
Then for the two remaining patches I've implemented most of what
Thomas suggest, e.g. the existing functionality sticks around for
eviction and hobs, but ttm_bo_validate will now try to always move
things into the non-fallback placements on validation first.
What I haven't done yet is to split up the preferred placement since
I couldn't immediately see an use case for this, but it's really
something we might do in the future as well.
Please review and comment,
Christian.
next reply other threads:[~2024-01-26 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 14:09 Christian König [this message]
2024-01-26 14:09 ` [PATCH 1/2] drm/ttm: improve idle/busy handling v4 Christian König
2024-02-06 12:53 ` Thomas Hellström
2024-02-06 12:56 ` Christian König
2024-02-23 14:30 ` Christian König
2024-02-26 20:21 ` Thomas Hellström
2024-02-27 8:12 ` Matthew Auld
2024-02-27 8:33 ` Christian König
2024-01-26 14:09 ` [PATCH 2/2] drm/amdgpu: use GTT only as fallback for VRAM|GTT Christian König
-- strict thread matches above, loose matches on Subject: below --
2024-01-12 12:51 Rework TTMs busy handling Christian König
2024-01-16 9:57 ` Christian König
2024-01-17 3:13 ` Zack Rusin
2024-01-09 7:47 Christian König
2024-01-09 8:14 ` Thomas Hellström
2024-01-09 8:34 ` Christian König
2024-01-10 9:03 ` Michel Dänzer
2024-01-04 15:05 Christian König
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=20240126140916.1577-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).