All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-xe@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm/xe: Don't fail runtime suspend permanently on VRAM eviction -ENOMEM
Date: Tue, 20 Oct 2026 09:08:43 -0700	[thread overview]
Message-ID: <ateSC6dTa0M3Qc8n@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <atduGDrVk7kc-PPe@intel.com>

On Tue, Oct 20, 2026 at 09:35:20AM -0400, Rodrigo Vivi wrote:
> On Tue, Oct 20, 2026 at 12:05:45PM +0200, Thomas Hellström wrote:
> > If evicting VRAM to system memory fails with -ENOMEM during runtime
> > suspend to D3cold, the error is returned to the runtime PM core.
> > Runtime PM treats any error other than -EAGAIN or -EBUSY from the
> > ->runtime_suspend() callback as fatal, records it in
> > dev->power.runtime_error, and refuses further runtime PM operations
> > on the device until the error is cleared.
> 
> oh!
> 

I'm poked around core PM code but had a hard time verifying the above
claim is correct.

Any code references to help me verify this is correct?

Matt

> > 
> > Memory shortage is a transient condition, and with eviction now using
> > __GFP_RETRY_MAYFAIL it is also more likely to occur. Convert -ENOMEM
> > from the eviction to -EAGAIN so that the device stays active and
> > runtime suspend is retried at a later idle transition.
> > 
> > Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
> > Cc: Matthew Brost <matthew.brost@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: intel-xe@lists.freedesktop.org
> > Cc: <stable@vger.kernel.org> # v6.8+
> > Assisted-by: LLM
> > Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_pm.c | 10 +++++++++-
> >  1 file changed, 9 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> > index daa7ba2df317..9bf57ed1ea59 100644
> > --- a/drivers/gpu/drm/xe/xe_pm.c
> > +++ b/drivers/gpu/drm/xe/xe_pm.c
> > @@ -649,8 +649,16 @@ int xe_pm_runtime_suspend(struct xe_device *xe)
> >  
> >  	if (xe->d3cold.allowed) {
> >  		err = xe_bo_evict_all(xe);
> > -		if (err)
> > +		if (err) {
> > +			/*
> > +			 * Runtime PM treats errors other than -EAGAIN and
> > +			 * -EBUSY as fatal, so report memory shortage as
> > +			 * transient to allow a later retry.
> > +			 */
> > +			if (err == -ENOMEM)
> > +				err = -EAGAIN;
> 
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> 
> >  			goto out_resume;
> > +		}
> >  	}
> >  
> >  	for_each_gt(gt, xe, id) {
> > -- 
> > 2.56.0
> > 

  reply	other threads:[~2026-10-20 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 10:05 [PATCH] drm/xe: Don't fail runtime suspend permanently on VRAM eviction -ENOMEM Thomas Hellström
2026-10-20 10:24 ` sashiko-bot
2026-10-20 12:42 ` ✓ CI.KUnit: success for " Patchwork
2026-10-20 13:20 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-20 13:35 ` [PATCH] " Rodrigo Vivi
2026-10-20 16:08   ` Matthew Brost [this message]
2026-10-20 16:37 ` ✓ Xe.CI.FULL: success for " Patchwork

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=ateSC6dTa0M3Qc8n@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=stable@vger.kernel.org \
    --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 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.