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: Wed, 29 Mar 2017 15:16:04 -0700 From: "Doug Smythies" <dsmythies@...us.net> To: "'Rafael J. Wysocki'" <rjw@...ysocki.net> Cc: "'Srinivas Pandruvada'" <srinivas.pandruvada@...ux.intel.com>, "'LKML'" <linux-kernel@...r.kernel.org>, "'Linux PM'" <linux-pm@...r.kernel.org>, "'Doug Smythies'" <dsmythies@...us.net> Subject: RE: [Update][PATCH v3 2/3] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy Hi Rafael, Disregard. I see this was fixed in kernel 4.11-rc4. While kernel 4.11-rc4 was where I thought I started from earlier, actually I was running 4.11-rc2 at the time. sorry for the noise. On 2017.03.29 15:01 Doug Smythies wrote: > Sorry for the delay, but I didn't notice until today that this > commit causes a regression, at least in my computer. > > I have not figured out exactly what is wrong, as I must > admit I am finding these policy interactions difficult > to follow. > > On 2017.03.02 14:29 Rafael J. Wysocki wrote: >>From: Rafael J. Wysocki <rafael.j.wysocki@...el.com> >> >> If the current P-state selection algorithm is set to "performance" >> in intel_pstate_set_policy(), the limits may be initialized from > > ... [cut] ... > > Going back to kernel 4.11-rc1 I get this after boot**: > > $ uname -a > Linux s15 4.11.0-rc1-stock #217 SMP Sun Mar 5 15:34:38 PST 2017 x86_64 x86_64 x86_64 GNU/Linux
Powered by blists - more mailing lists