From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [Intel-gfx] [PATCH v2 0/4] drm/ttm: Fixes around resources and bulk moves
Date: Tue, 27 Jun 2023 11:05:45 +0200 [thread overview]
Message-ID: <f821b9e3-b4b1-d182-040f-27df81cf8aa6@linux.intel.com> (raw)
In-Reply-To: <20230626091450.14757-1-thomas.hellstrom@linux.intel.com>
On 6/26/23 11:14, Thomas Hellström wrote:
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> A couple of ttm fixes for issues that either were hit while developing the
> xe driver or, for the resource leak patches, discovered during code
> inspection.
>
> v2:
> - Avoid a goto in patch 3 (Andi Shyti)
> - Add some RB's
>
> Thomas Hellström (4):
> drm/ttm: Fix ttm_lru_bulk_move_pos_tail()
> drm/ttm: Don't shadow the operation context
> drm/ttm: Don't leak a resource on eviction error
> drm/ttm: Don't leak a resource on swapout move error
>
> drivers/gpu/drm/ttm/ttm_bo.c | 26 +++++++++++++-------------
> drivers/gpu/drm/ttm/ttm_resource.c | 2 ++
> 2 files changed, 15 insertions(+), 13 deletions(-)
>
Pushed 2/4 to drm-misc-next, 3/4 & 4/4 to drm-misc-fixes.
/Thomas
prev parent reply other threads:[~2023-06-27 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 9:14 [Intel-gfx] [PATCH v2 0/4] drm/ttm: Fixes around resources and bulk moves Thomas Hellström
2023-06-26 9:14 ` [Intel-gfx] [PATCH v2 1/4] drm/ttm: Fix ttm_lru_bulk_move_pos_tail() Thomas Hellström
2023-06-26 10:21 ` Christian König
2023-06-26 9:14 ` [Intel-gfx] [PATCH v2 2/4] drm/ttm: Don't shadow the operation context Thomas Hellström
2023-06-26 15:15 ` Christian König
2023-06-26 15:18 ` Thomas Hellström
2023-06-26 15:23 ` [Intel-gfx] [Intel-xe] " Thomas Hellström
2023-06-26 9:14 ` [Intel-gfx] [PATCH v2 3/4] drm/ttm: Don't leak a resource on eviction error Thomas Hellström
2023-06-26 11:24 ` Andi Shyti
2023-06-26 11:32 ` Christian König
2023-06-26 9:14 ` [Intel-gfx] [PATCH v2 4/4] drm/ttm: Don't leak a resource on swapout move error Thomas Hellström
2023-06-26 11:33 ` Christian König
2023-06-26 12:23 ` Thomas Hellström
2023-06-26 14:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/ttm: Fixes around resources and bulk moves (rev2) Patchwork
2023-06-27 0:32 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-06-27 9:05 ` Thomas Hellström [this message]
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=f821b9e3-b4b1-d182-040f-27df81cf8aa6@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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