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-next>] [day] [month] [year] [list]
Message-Id: <20201003131938.9426-1-hdegoede@redhat.com>
Date:   Sat,  3 Oct 2020 15:19:37 +0200
From:   Hans de Goede <hdegoede@...hat.com>
To:     Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>,
        Mark Gross <mgross@...ux.intel.com>
Cc:     Hans de Goede <hdegoede@...hat.com>,
        Mario Limonciello <mario.limonciello@...l.com>,
        Mark Pearson <mpearson@...ovo.com>,
        Elia Devito <eliadevito@...il.com>,
        Bastien Nocera <hadess@...ess.net>,
        Benjamin Berg <bberg@...hat.com>, linux-pm@...r.kernel.org,
        linux-acpi@...r.kernel.org, platform-driver-x86@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: [RFC 0/1] Documentation: Add documentation for new performance_profile sysfs class

Hi All,

Recently 2 different patches have been submitted for drivers under
drivers/platform/x86 to configure the performance-profile of
modern laptops (see the actual RFC patch for what I mean with
a performance-profile). One for the thinkpad_acpi driver and
one for the hp-wmi driver.

Since I don't want each pdx86 driver to invent its own userspace API
for this I have started a dicussion about coming up with a standardized /
common sysfs class / API for this on the pdx86 list:
https://www.spinics.net/lists/platform-driver-x86/msg22794.html

The sysfs API proposal which I'm sending out as RFC in this email
thread is the result of me trying to distill that discussion into
a concrete proposal.

I have Cc-ed the linux-pm and linux-acpi lists because even though
the trigger for doing this is 2 different pdx86 drivers, the resulting
API should (must even) also be suitable for other platforms. I can
e.g. see various modern ARM platforms also having similar functionality
which they may want to export to userspace and the ideally the userspace
code for allowing the end-user to configure/select a profile would be
the same under ARM and x86.

Talking about userspace I've also Cc-ed Bastien and Benjamin who are
working on the userspace side of this.

Regards,

Hans

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ