All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Maarten Lankhorst <dev@lankhorst.se>, intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/xe: Attempt to bring bos back to VRAM after eviction
Date: Fri, 29 Aug 2025 12:55:36 +0200	[thread overview]
Message-ID: <692711fadc25a6c85c19ae16e9c04e50f1eaa3a9.camel@linux.intel.com> (raw)
In-Reply-To: <e8a176ab-a24c-4b9d-a046-ae386f08f129@lankhorst.se>

On Fri, 2025-08-29 at 09:42 +0200, Maarten Lankhorst wrote:
> Hey,
> 
> Den 2025-08-28 kl. 17:42, skrev Thomas Hellström:
> > VRAM+TT bos that are evicted from VRAM to TT may remain in
> > TT also after a revalidation following eviction or suspend.
> > 
> > This manifests itself as applications becoming sluggish
> > after buffer objects get evicted or after a resume from
> > suspend or hibernation.
> > 
> > If the bo supports placement in both VRAM and TT, and
> > we are on DGFX, mark the TT placement as fallback. This means
> > that it is tried only after VRAM + eviction.
> > 
> > This flaw has probably been present since the xe module was
> > upstreamed but use a Fixes: commit below where backporting is
> > likely to be simple. For earlier versions we need to open-
> > code the fallback algorithm in the driver.
> > 
> > Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/5995
> > Fixes: a78a8da51b36 ("drm/ttm: replace busy placement with flags
> > v6")
> I'd say it this closes a bug in the original driver, although
> effectively v6.8 is no longer supported anyway.
> 
> Should DESIRED also be set on the add_vram flags?

It looks for me from the TTM code that TTM then *skips* the placement
when doing a second pass with evictions.

So that's not really what we want IMO.

/Thomas

> 
> > Cc: Matthew Brost <matthew.brost@intel.com>
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Cc: <stable@vger.kernel.org> # v6.9+
> > Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_bo.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_bo.c
> > b/drivers/gpu/drm/xe/xe_bo.c
> > index 4faf15d5fa6d..64dea4e478bd 100644
> > --- a/drivers/gpu/drm/xe/xe_bo.c
> > +++ b/drivers/gpu/drm/xe/xe_bo.c
> > @@ -188,6 +188,8 @@ static void try_add_system(struct xe_device
> > *xe, struct xe_bo *bo,
> >  
> >  		bo->placements[*c] = (struct ttm_place) {
> >  			.mem_type = XE_PL_TT,
> > +			.flags = (IS_DGFX(xe) && (bo_flags &
> > XE_BO_FLAG_VRAM_MASK)) ?
> > +			TTM_PL_FLAG_FALLBACK : 0,
> >  		};
> >  		*c += 1;
> >  	}
> 
> Kind regards,
> ~Maarten Lankhorst


  reply	other threads:[~2025-08-29 10:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 15:42 [PATCH] drm/xe: Attempt to bring bos back to VRAM after eviction Thomas Hellström
2025-08-28 15:59 ` Matthew Auld
2025-08-28 16:06   ` Thomas Hellström
2025-08-28 16:27     ` Matthew Auld
2025-08-28 18:06       ` Thomas Hellström
2025-08-28 18:06 ` ✓ CI.KUnit: success for " Patchwork
2025-08-28 19:12 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-08-29  1:06 ` ✗ Xe.CI.Full: " Patchwork
2025-08-29  7:42 ` [PATCH] " Maarten Lankhorst
2025-08-29 10:55   ` Thomas Hellström [this message]
2025-08-29 11:21     ` Maarten Lankhorst

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=692711fadc25a6c85c19ae16e9c04e50f1eaa3a9.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=dev@lankhorst.se \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.