From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Mario Limonciello" <superm1@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Pavel Machek" <pavel@kernel.org>, "Len Brown" <lenb@kernel.org>,
"Christian König" <christian.koenig@amd.com>,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"open list:HIBERNATION (aka Software Suspend,
aka swsusp)" <linux-pm@vger.kernel.org>,
"open list:RADEON and AMDGPU DRM DRIVERS"
<amd-gfx@lists.freedesktop.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
"open list:SCSI SUBSYSTEM" <linux-scsi@vger.kernel.org>,
"open list:USB SUBSYSTEM" <linux-usb@vger.kernel.org>,
"open list:TRACING" <linux-trace-kernel@vger.kernel.org>,
"AceLan Kao" <acelan.kao@canonical.com>,
"Kai-Heng Feng" <kaihengf@nvidia.com>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
"Merthan Karakaş" <m3rthn.k@gmail.com>,
"Eric Naim" <dnaim@cachyos.org>
Subject: Re: [PATCH v6 00/11] Improvements to S5 power consumption
Date: Sat, 6 Sep 2025 14:20:00 +0200 [thread overview]
Message-ID: <2025090644-connected-coping-fbd2@gregkh> (raw)
In-Reply-To: <CAJZ5v0hLO5xhmjniO4=rLK1JK9OM8naxXVEGuHUT3cuhRp=Atw@mail.gmail.com>
On Wed, Sep 03, 2025 at 01:14:18PM +0200, Rafael J. Wysocki wrote:
> On Wed, Sep 3, 2025 at 6:41 AM Mario Limonciello <superm1@kernel.org> wrote:
> >
> > On 8/17/2025 9:00 PM, Mario Limonciello (AMD) wrote:
> > > A variety of issues both in function and in power consumption have been
> > > raised as a result of devices not being put into a low power state when
> > > the system is powered off.
> > >
> > > There have been some localized changes[1] to PCI core to help these issues,
> > > but they have had various downsides.
> > >
> > > This series instead tries to use the S4 flow when the system is being
> > > powered off. This lines up the behavior with what other operating systems
> > > do as well. If for some reason that fails or is not supported, run their
> > > shutdown() callbacks.
> > >
> > > Cc: AceLan Kao <acelan.kao@canonical.com>
> > > Cc: Kai-Heng Feng <kaihengf@nvidia.com>
> > > Cc: Mark Pearson <mpearson-lenovo@squebb.ca>
> > > Cc: Merthan Karakaş <m3rthn.k@gmail.com>
> > > Cc: Eric Naim <dnaim@cachyos.org>
> > > ---
> > > v5->v6:
> > > * Fix for LKP robot issue
> > > * Some commit message changes
> > > * Rebase on 6.17-rc2
> > >
> > > Mario Limonciello (AMD) (11):
> > > PM: Introduce new PMSG_POWEROFF event
> > > scsi: Add PM_EVENT_POWEROFF into suspend callbacks
> > > usb: sl811-hcd: Add PM_EVENT_POWEROFF into suspend callbacks
> > > USB: Pass PMSG_POWEROFF event to suspend_common() for poweroff with S4
> > > flow
> > > PCI: PM: Disable device wakeups when halting system through S4 flow
> > > PCI: PM: Split out code from pci_pm_suspend_noirq() into helper
> > > PCI: PM: Run bridge power up actions as part of restore phase
> > > PCI: PM: Use pci_power_manageable() in pci_pm_poweroff_noirq()
> > > PCI: Put PCIe bridges with downstream devices into D3 at hibernate
> > > drm/amd: Avoid evicting resources at S5
> > > PM: Use hibernate flows for system power off
> > >
> > > drivers/base/power/main.c | 7 ++
> > > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 4 +
> > > drivers/pci/pci-driver.c | 99 +++++++++++++++-------
> > > drivers/scsi/mesh.c | 1 +
> > > drivers/scsi/stex.c | 1 +
> > > drivers/usb/core/hcd-pci.c | 11 ++-
> > > drivers/usb/host/sl811-hcd.c | 1 +
> > > include/linux/pm.h | 5 +-
> > > include/trace/events/power.h | 3 +-
> > > kernel/reboot.c | 6 ++
> > > 10 files changed, 103 insertions(+), 35 deletions(-)
> > >
> >
> > Rafael, Bjorn,
> >
> > Any feedback for this series?
>
> I still have the same basic concern as before: It is an intrusive
> change likely to cause regressions to occur.
>
> It also changes the driver ABI quite dramatically because different
> callbacks will now be used for system shutdown and kexec, for example,
> at least on some platforms.
>
> Frankly, I'd like to know Greg's and Danilo's opinions on the direction here.
>
I've been ignoring this, sorry. Can someone resend the series and ask
for my review then?
thanks,
greg k-h
prev parent reply other threads:[~2025-09-06 12:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:00 [PATCH v6 00/11] Improvements to S5 power consumption Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 01/11] PM: Introduce new PMSG_POWEROFF event Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 02/11] scsi: Add PM_EVENT_POWEROFF into suspend callbacks Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 03/11] usb: sl811-hcd: " Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 04/11] USB: Pass PMSG_POWEROFF event to suspend_common() for poweroff with S4 flow Mario Limonciello (AMD)
2025-08-18 10:50 ` Oliver Neukum
2025-08-18 11:24 ` Mario Limonciello
2025-08-18 2:00 ` [PATCH v6 05/11] PCI: PM: Disable device wakeups when halting system through " Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 06/11] PCI: PM: Split out code from pci_pm_suspend_noirq() into helper Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 07/11] PCI: PM: Run bridge power up actions as part of restore phase Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 08/11] PCI: PM: Use pci_power_manageable() in pci_pm_poweroff_noirq() Mario Limonciello (AMD)
2025-08-18 2:00 ` [PATCH v6 09/11] PCI: Put PCIe bridges with downstream devices into D3 at hibernate Mario Limonciello (AMD)
2025-08-18 2:01 ` [PATCH v6 10/11] drm/amd: Avoid evicting resources at S5 Mario Limonciello (AMD)
2025-08-18 2:01 ` [PATCH v6 11/11] PM: Use hibernate flows for system power off Mario Limonciello (AMD)
2025-09-03 4:41 ` [PATCH v6 00/11] Improvements to S5 power consumption Mario Limonciello
2025-09-03 11:14 ` Rafael J. Wysocki
2025-09-06 12:20 ` Greg Kroah-Hartman [this message]
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=2025090644-connected-coping-fbd2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=acelan.kao@canonical.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dnaim@cachyos.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kaihengf@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m3rthn.k@gmail.com \
--cc=martin.petersen@oracle.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=superm1@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 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).