All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lyude Paul <lyude@redhat.com>
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Timur Tabi <ttabi@nvidia.com>,
	Dave Airlie <airlied@redhat.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Ben Skeggs <bskeggs@nvidia.com>, Kees Cook <kees@kernel.org>,
	Simona Vetter <simona@ffwll.ch>, David Airlie <airlied@gmail.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Maxime Ripard <mripard@kernel.org>,
	Mel Henning <mhenning@darkrefraction.com>,
	Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v2 0/4] drm/nouveau/gsp/r570: Fix runtime PM
Date: Tue, 30 Jun 2026 14:50:28 +0300	[thread overview]
Message-ID: <akOthKT6XeaUnhH6@ashevche-desk.local> (raw)
In-Reply-To: <20260629224350.2870201-1-lyude@redhat.com>

On Mon, Jun 29, 2026 at 06:42:32PM -0400, Lyude Paul wrote:
> Runtime PM has been kind of unreliable with GSP for a while. It works
> well enough to shut the GPU off and turn it back on, but more often then
> not it ends up leaving the GPU in a broken state on resume - which makes
> it impossible to really do anything else with it.
> 
> Recently however, I discovered that it's been failing much harder on
> some ampere systems. This lead me down a rabbit hole that lead me to
> figure out one of our previous fixes for runtime PM wasn't correct.
> After fixing that and combining it with some fixes we had tried in the
> past without success, I finally managed to get nouveau to handle runtime
> PM with the GSP perfectly. These are those fixes.
> 
> Tested on a Lenovo P16 G1 (100 runtime PM cycles!), and RTX4000.

This is v2, and no changelog. What's going on?

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lyude Paul <lyude@redhat.com>
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Ben Skeggs <bskeggs@nvidia.com>, Kees Cook <kees@kernel.org>,
	Simona Vetter <simona@ffwll.ch>,
	Maxime Ripard <mripard@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v2 0/4] drm/nouveau/gsp/r570: Fix runtime PM
Date: Tue, 30 Jun 2026 14:50:28 +0300	[thread overview]
Message-ID: <akOthKT6XeaUnhH6@ashevche-desk.local> (raw)
In-Reply-To: <20260629224350.2870201-1-lyude@redhat.com>

On Mon, Jun 29, 2026 at 06:42:32PM -0400, Lyude Paul wrote:
> Runtime PM has been kind of unreliable with GSP for a while. It works
> well enough to shut the GPU off and turn it back on, but more often then
> not it ends up leaving the GPU in a broken state on resume - which makes
> it impossible to really do anything else with it.
> 
> Recently however, I discovered that it's been failing much harder on
> some ampere systems. This lead me down a rabbit hole that lead me to
> figure out one of our previous fixes for runtime PM wasn't correct.
> After fixing that and combining it with some fixes we had tried in the
> past without success, I finally managed to get nouveau to handle runtime
> PM with the GSP perfectly. These are those fixes.
> 
> Tested on a Lenovo P16 G1 (100 runtime PM cycles!), and RTX4000.

This is v2, and no changelog. What's going on?

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-06-30 11:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 22:42 [PATCH v2 0/4] drm/nouveau/gsp/r570: Fix runtime PM Lyude Paul
2026-06-29 22:42 ` Lyude Paul
2026-06-29 22:42 ` [PATCH v2 1/4] Revert "nouveau/gsp: fix suspend/resume regression on r570 firmware" Lyude Paul
2026-06-29 22:42   ` Lyude Paul
2026-06-29 22:56   ` sashiko-bot
2026-06-30 11:53   ` Andy Shevchenko
2026-06-30 11:53     ` Andy Shevchenko
2026-06-30 16:05     ` Danilo Krummrich
2026-06-30 16:05       ` Danilo Krummrich
2026-07-01 18:16       ` lyude
2026-07-01 18:16         ` lyude
2026-06-29 22:42 ` [PATCH v2 2/4] drm/nouveau/gsp/r570: Never enter Gcoff state Lyude Paul
2026-06-29 22:42   ` Lyude Paul
2026-06-29 22:56   ` sashiko-bot
2026-06-29 22:42 ` [PATCH v2 3/4] drm/nouveau/gsp/r570: Set oldLevel correctly in GSP resume arguments Lyude Paul
2026-06-29 22:42   ` Lyude Paul
2026-06-29 22:42 ` [PATCH v2 4/4] drm/nouveau/gsp/r570: Add missing state flags to " Lyude Paul
2026-06-29 22:42   ` Lyude Paul
2026-06-30 11:50 ` Andy Shevchenko [this message]
2026-06-30 11:50   ` [PATCH v2 0/4] drm/nouveau/gsp/r570: Fix runtime PM Andy Shevchenko
2026-07-01 18:05   ` lyude
2026-07-01 18:05     ` lyude

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=akOthKT6XeaUnhH6@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=bskeggs@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mhenning@darkrefraction.com \
    --cc=mripard@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=simona@ffwll.ch \
    --cc=ttabi@nvidia.com \
    --cc=tzimmermann@suse.de \
    /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.