linux-kernel - Re: [RFC v1 0/8] acpi/x86: s2idle: Introduce and implement runtime standby ABI for ACPI s0ix platforms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ab4d90d8-3212-4571-9f92-ac4facd3aa33@collabora.com>
Date: Thu, 15 Jan 2026 02:07:02 +0300
From: Dmitry Osipenko <dmitry.osipenko@...labora.com>
To: Antheas Kapenekakis <lkml@...heas.dev>
Cc: bob.beckett@...labora.com, bookeldor@...il.com, hadess@...ess.net,
 jaap@...tsma.org, kernel@...labora.com, lennart@...ttering.net,
 linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org, mccann@....edu,
 rafael@...nel.org, richard@...hsie.com, sebastian.reichel@...labora.com,
 superm1@...nel.org, systemd-devel@...ts.freedesktop.org,
 xaver.hugl@...il.com, John Schoenick <johns@...vesoftware.com>
Subject: Re: [RFC v1 0/8] acpi/x86: s2idle: Introduce and implement runtime
 standby ABI for ACPI s0ix platforms

On 1/13/26 13:11, Antheas Kapenekakis wrote:
> On Tue, 13 Jan 2026 at 11:50, Dmitry Osipenko
> <dmitry.osipenko@...labora.com> wrote:
>>
>> Hello,
>>
>> On 1/12/26 23:33, Antheas Kapenekakis wrote:
>>> On Fri, 26 Dec 2025 at 12:27, Antheas Kapenekakis <lkml@...heas.dev> wrote:
>>>>
>>>> This series introduces a new runtime standby ABI to allow firing Modern
>>>> Standby firmware notifications that modify hardware appearance from userspace
>>>> without suspending the kernel. This allows userspace to set the inactivity
>>>> state of the device so that it looks like it is asleep (e.g., flashing the
>>>> power button) while still being able to perform basic computations.
>>>>
>>>> snip
>>>>
>>>> base-commit: 9448598b22c50c8a5bb77a9103e2d49f134c9578
>>>> --
>>>> 2.52.0
>>>>
>>>
>>> Happy new year everyone
>>>
>>> Small bump on this as all of us are starting to get back from holidays
>>>
>>> I still have to bump an asus series before I get back to this. I would
>>> appreciate some feedback in the interim.
>>>
>>> I think targeting 6.20/7.0? is unrealistic so there is no rush from my side
>>>
>>> Antheas
>>
>> Thanks a lot for sending these patches! I briefly looked through them
>> last week and will make another iteration soon.
> 
> Hi Dmitry,
> can you expand a bit on your use-case/KPIs/timeline for your series?
> 
> Is it handhelds/laptops or what is the intended use-case?
> 
> [2] before the rewrite had been tested on most handheld makes and SKUs
> (over 70 models) and laptop manufacturers and it performs as expected.
> As it is multiple months of research I'd like to get some credit for it.
> 
> Happy to collaborate in any case, especially if you will log hours on
> this and can push a variant through faster. I am not sure if starting
> from scratch is worthwhile for either of us

The primary goal is to support screen-off DSM for a power-efficient
background games downloading [1] and further resume-to-dark on Steam
Deck and other handhelds. There is no strict timeline, usual "sooner the
better". Downstreams will use customized WIP solution till upstream will
get necessary generic interfaces.

[1] https://store.steampowered.com/news/app/1675200/view/771930569635267984

A common approach for upstreaming is to divide problem into smaller
manageable parts. That's what I'm planning to focus on now to see if we
can start easy with a minimal changes.

Please don't worry about the credit. You did a significant ground work
that is well recognized by now. Thanks a lot for your efforts and help.
Starting from scratch of course won't be a good approach with all the
broad testing you've done.

-- 
Best regards,
Dmitry