From: Hans de Goede <hdegoede@redhat.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-pm@vger.kernel.org
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Add some extra debugging mechanisms for s0i3
Date: Fri, 9 Sep 2022 18:01:02 +0200 [thread overview]
Message-ID: <75e632e6-07df-5b97-d9d7-c4b60a5a3b9b@redhat.com> (raw)
In-Reply-To: <20220829162953.5947-1-mario.limonciello@amd.com>
Hi All,
On 8/29/22 18:29, Mario Limonciello wrote:
> Recently there have been reports of problems where the system consumes
> too much power after certain interrupts occur that would notify the
> kernel of some event but those events aren't marked for wakeup.
>
> These problems have been root caused to the timing of the kernel moving
> the cores into ACPI C3 relative to other events from the previous wakeup
> not being settled. Linux will more aggressively move the cores into C3
> for s2idle than Windows does for Modern Standby.
>
> To aide with debugging this class of problems in the future add a new
> set of optional debugging infrastructure.
>
> Mario Limonciello (4):
> ACPI: s2idle: Add a new ->check() callback for platform_s2idle_ops
> platform/x86/amd: pmc: Add defines for STB events
> platform/x86/amd: pmc: Always write to the STB
> platform/x86/amd: pmc: Add an extra STB message for checking s2idle
> entry
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
>
> drivers/acpi/sleep.h | 1 +
> drivers/acpi/x86/s2idle.c | 14 ++++++++++++++
> drivers/platform/x86/amd/pmc.c | 32 ++++++++++++++++++++------------
> include/linux/acpi.h | 1 +
> include/linux/suspend.h | 1 +
> kernel/power/suspend.c | 3 +++
> 6 files changed, 40 insertions(+), 12 deletions(-)
>
prev parent reply other threads:[~2022-09-09 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 16:29 Mario Limonciello
2022-08-29 16:29 ` [PATCH v3 1/4] ACPI: s2idle: Add a new ->check() callback for platform_s2idle_ops Mario Limonciello
2022-08-30 11:39 ` Rafael J. Wysocki
2022-08-30 11:42 ` Limonciello, Mario
2022-08-30 14:50 ` Hans de Goede
2022-08-29 16:29 ` [PATCH v3 2/4] platform/x86/amd: pmc: Add defines for STB events Mario Limonciello
2022-08-29 16:29 ` [PATCH v3 3/4] platform/x86/amd: pmc: Always write to the STB Mario Limonciello
2022-08-29 16:29 ` [PATCH v3 4/4] platform/x86/amd: pmc: Add an extra STB message for checking s2idle entry Mario Limonciello
2022-09-09 16:01 ` Hans de Goede [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=75e632e6-07df-5b97-d9d7-c4b60a5a3b9b@redhat.com \
--to=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®