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
| ||
|
Date: Tue, 1 Nov 2022 09:50:26 -0400 From: Sven van Ashbrook <svenva@...omium.org> To: Mario Limonciello <mario.limonciello@....com> Cc: Rajneesh Bhardwaj <irenic.rajneesh@...il.com>, Hans de Goede <hdegoede@...hat.com>, LKML <linux-kernel@...r.kernel.org>, "S-k, Shyam-sundar" <Shyam-sundar.S-k@....com>, "rrangel@...omium.org" <rrangel@...omium.org>, "platform-driver-x86@...r.kernel.org" <platform-driver-x86@...r.kernel.org>, Rajneesh Bhardwaj <rajneesh.bhardwaj@...el.com>, Rafael J Wysocki <rjw@...ysocki.net>, Rajat Jain <rajatja@...gle.com>, David E Box <david.e.box@...el.com>, Mark Gross <markgross@...nel.org> Subject: Re: [PATCH v1] platform/x86: intel_pmc_core: promote S0ix failure warn() to WARN() On Mon, Oct 31, 2022 at 9:58 PM Mario Limonciello <mario.limonciello@....com> wrote: > > I actually thought that by putting the duration of time put in > last_hw_deepest_state you'll be able to catch this by comparing the > duration of the suspend to the duration of last_hw_deepest_state. I'm not sure if this method would catch all or even most suspend failures. That's why the EC monitoring of S0ix was devised. I will circulate this internally, see what comes back. > > > > Is the light worth the candle? > > I wrote an RFC that I sent out for it with my ideas at least. > That is much appreciated ! Yet even for good ideas, it's often necessary to weigh the benefits and downsides of the intervention. Perhaps we can get some pros/cons feedback from other stakeholders ? Sven
Powered by blists - more mailing lists