intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
	christian.koenig@amd.com, thomas.hellstrom@linux.intel.com,
	ecourtney@nvidia.com, nat@pixelcluster.dev,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 01/10] dma-buf: Add reference counting to dma_resv
Date: Fri, 28 Aug 2026 12:34:27 -0700	[thread overview]
Message-ID: <apHiw91fFbKuogDJ@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <apHe5YcWWiZF4i2Z@gsse-cloud1.jf.intel.com>

On Fri, Aug 28, 2026 at 12:17:57PM -0700, Matthew Brost wrote:
> On Fri, Aug 28, 2026 at 08:21:17PM +0200, Danilo Krummrich wrote:
> > On Thu Aug 27, 2026 at 2:38 PM CEST, =?UTF-8?q?Christian=20K=C3=B6nig?= wrote:
> > > This provides clearer ownership semantics and makes the code more
> > > maintainable by removing the embedded allocation hack.
> > 
> > Again, fundamentally disagree; please see [1] for details and reasons.
> > 
> 
> I think Christian is doing this incrementally rather than as a single
> change across the tree. The last patch [2] in the series removes
> `dma_resv_init` and the `allocated` flag. I believe that was the main
> concern, and it appears to be addressed now.
> 
> I'm taking the series for a spin now, as our CI [3] had trouble applying
> this patch. I'll let you know what my testing shows.
> 

I ran our basic CI suite and didn't see any regressions. I also ran some
eviction and shrinker tests that stress interactions with active fences
and exercise individualization paths, and those passed as well.

Matt

> [2] https://patchwork.freedesktop.org/patch/748868/?series=172875&rev=1
> [3] https://patchwork.freedesktop.org/series/172873/
> 
> > Besides that, I don't really know what to expect from the series. The cover
> > letter says "Refcounting dma_resv v2", yet there's no changelog telling people
> > what has changed since v1. On the other hand, none of the patches has a v2
> > prefix, so what is it?
> 
> Yes, change logs / cover-letter would help as Danilo likely could have
> spotted the above change.
> 
> Matt
> 
> > 
> > [1] https://lore.kernel.org/all/DJVRML4G11GZ.Z7FTZH7I1LZN@kernel.org/

  reply	other threads:[~2026-08-28 19:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 12:38 Refcounting dma_resv v2 Christian König
2026-08-27 12:38 ` [PATCH 01/10] dma-buf: Add reference counting to dma_resv Christian König
2026-08-27 18:39   ` Andi Shyti
2026-08-28 18:21   ` Danilo Krummrich
2026-08-28 19:17     ` Matthew Brost
2026-08-28 19:34       ` Matthew Brost [this message]
2026-08-27 12:38 ` [PATCH 02/10] dma-buf/tests: Convert st-dma-resv tests to use dma_resv_alloc Christian König
2026-08-27 13:08   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 03/10] drm/gem: Add helper for drm_gem_object resv assignment Christian König
2026-08-27 13:22   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 04/10] drm/gem: Convert drm_gem_private_object_init to return error code Christian König
2026-08-27 13:19   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 05/10] drm/gem: Use dynamic allocation for GEM object dma_resv Christian König
2026-08-27 13:13   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 06/10] drm/mode_config: Use dma_resv_alloc for lockdep annotation Christian König
2026-08-27 13:02   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 07/10] drm/xe: " Christian König
2026-08-27 13:04   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 08/10] drm/i915/gt: Use dma_resv_alloc for VM reservation objects Christian König
2026-08-27 13:11   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 09/10] drm/ttm/tests: Use dma_resv_alloc in test files Christian König
2026-08-27 13:12   ` sashiko-bot
2026-08-27 12:38 ` [PATCH 10/10] dma-buf: Inline dma_resv_init and remove allocated flag Christian König
2026-08-27 13:31   ` sashiko-bot

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=apHiw91fFbKuogDJ@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ecourtney@nvidia.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=nat@pixelcluster.dev \
    --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 NNTP newsgroup(s).