lkml.org 
[lkml]   [2022]   [Nov]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [RFC 1/3] PM: Add a sysfs file to represent whether hardware reached the deepest state
From
On 11/1/2022 12:37, Sven van Ashbrook wrote:
> On Mon, Oct 31, 2022 at 4:43 PM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>>
>> +void pm_set_hw_deepest_state(u64 duration)
>> +{
>> + suspend_stats.last_hw_deepest_state = duration;
>
> I'm wondering if we could add a userspace notification here. Then
> userspace wouldn't have to synchronize with the suspend/resume state
> of the system when reading this entry.
>
> What about sysfs_notify() ? Or via udev?

The question I would have is what kobj would you notify? power_kobj?
Lots of other things write to suspend stats, but nothing else sends
notifications. So why is this one going to be special?

To me I don't think it's much different for userspace to "always" read
the file after resume vs wait for the notification and then read it.

To make userspace flexible to multiple kernel versions it seems to me
that userspace could check if that file exists before suspend and if it
does then check the value after suspend.

>
>> +}
>> +EXPORT_SYMBOL_GPL(pm_set_hw_deepest_state);

\
 
 \ /
  Last update: 2022-11-01 20:59    [W:0.078 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site