Re: [PATCH v5 1/2] drm/panthor: Implement evicted status for GEM objects

[Boris Brezillon <boris.brezillon@collabora.com>]

On Thu, 21 May 2026 16:44:14 +0200
Nicolas Frattaroli <nicolas.frattaroli@collabora.com> wrote:

> On Thursday, 21 May 2026 15:51:15 Central European Summer Time Nicolas Frattaroli wrote:
> > For fdinfo to be able to fill its evicted counter with data, panthor
> > needs to keep track of whether a GEM object has ever been reclaimed.
> > Just checking whether the pages are resident isn't enough, as newly
> > allocated objects also won't be resident.
> > 
> > Do this with a new atomic_t member on panthor_gem_object. It's increased
> > when an object gets evicted by the shrinker, and saturates at INT_MAX.
> > This means that once an object has been evicted at least once, its
> > reclaim counter will never return to 0.
> > 
> > Due to this, it's possible to distinguish evicted non-resident pages
> > from newly allocated non-resident pages by checking whether
> > reclaimed_count is != 0
> > 
> > Use this new member to then set the appropriate DRM_GEM_OBJECT_EVICTED
> > status flag for fdinfo.
> >   
> 
> Oops, feel free to drop this paragraph in the commit message when
> applying.
> 
> 

Queued to drm-misc-next with this paragraph removed.

Thanks,

Boris