dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>,
	matthew.brost@intel.com, dri-devel@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org
Subject: Re: Switching over to GEM refcounts and a bunch of cleanups
Date: Thu, 21 Aug 2025 16:06:20 +0200	[thread overview]
Message-ID: <fd34b897a3223346518d3fe009772996eb25c90b.camel@linux.intel.com> (raw)
In-Reply-To: <1f13c0b6-fdbb-4364-a32e-4344f8526464@amd.com>

Hi Christian,

On Thu, 2025-08-21 at 14:30 +0200, Christian König wrote:
> On 04.08.25 14:24, Christian König wrote:
> > On 22.07.25 14:36, Thomas Hellström wrote:
> > > Hi, Christian,
> > > 
> > > On Wed, 2025-07-16 at 18:04 +0200, Christian König wrote:
> > > > Hi guys,
> > > > 
> > > > so I hope Thomas is back from vacation while I will be on
> > > > vacation
> > > > for
> > > > the next two weeks.
> > > > 
> > > > Here is the patch set which cleans up TTM and XE in preperation
> > > > of
> > > > switching to drm_exec.
> > > > 
> > > > Please take a look and let me know what you think about it.
> > > 
> > > I'll take a look.
> > > BTW Did you see my comments on patch 6/6 on v1, essentially I
> > > think
> > > both i915 and xe rejecting some TTM callbacks if the object is a
> > > zombie
> > > (the GEM refcount has reached 0).
> > 
> > Sorry for the delay I'm just back from vacation.
> > 
> > I have seen that XE and i915 is checking the GEM refcount, but I
> > haven't seen your comment on that.
> > 
> > Going to take a look ASAP.
> 
> I'm not able to find that mail.
> 
> All I've seen is your comment on the VMWGFX stuff and that was
> already resolved by Zack.
> 
> What are you referring to?

https://lore.kernel.org/intel-xe/a004736315d77837172418eb196d5b5f80b74e6c.camel@linux.intel.com/

Thanks,
Thomas


> 
> Thanks,
> Christian.
> 
> > 
> > Regards,
> > Christian.
> > 
> > > 
> > > Thanks,
> > > Thomas
> > > 
> > > 
> > > > 
> > > > Regards,
> > > > Christian.
> > > > 
> > > 
> > 
> 


  reply	other threads:[~2025-08-21 14:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 16:04 Switching over to GEM refcounts and a bunch of cleanups Christian König
2025-07-16 16:04 ` [PATCH 1/7] drm/ttm: replace TTMs refcount with the DRM refcount v3 Christian König
2025-07-16 16:04 ` [PATCH 2/7] drm/ttm: remove ttm_lru_walk_ops Christian König
2025-07-16 16:04 ` [PATCH 3/7] drm/ttm: grab BO reference before locking it Christian König
2025-07-16 16:04 ` [PATCH 4/7] drm/ttm: switch to ttm_bo_lru_for_each_reserved_guarded for swapout Christian König
2025-07-16 16:04 ` [PATCH 5/7] drm/ttm: move zombie handling into ttm_bo_evict Christian König
2025-07-16 16:04 ` [PATCH 6/7] drm/ttm: use ttm_bo_lru_for_each_reserved_guarded in evict_all Christian König
2025-07-16 16:04 ` [PATCH 7/7] drm/xe: remove workaround for TTM internals Christian König
2025-07-22 12:36 ` Switching over to GEM refcounts and a bunch of cleanups Thomas Hellström
2025-08-04 12:24   ` Christian König
2025-08-21 12:30     ` Christian König
2025-08-21 14:06       ` Thomas Hellström [this message]
2025-08-21 14:59         ` Christian König
2025-08-22  8:51           ` Thomas Hellström

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=fd34b897a3223346518d3fe009772996eb25c90b.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.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;
as well as URLs for NNTP newsgroup(s).