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: Fri, 07 Jun 2013 09:48:36 +0800 From: Joe Jin <joe.jin@...cle.com> To: "Rafael J. Wysocki" <rjw@...k.pl> CC: Viresh Kumar <viresh.kumar@...aro.org>, Neil Gu <qing.gu@...cle.com>, cpufreq@...r.kernel.org, linux-pm@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] ACPI: update user_policy.max when _PPC updated On 06/07/13 03:54, Rafael J. Wysocki wrote: > Do you mean you set a limit in the BIOS setup and the kernel changed that limit > on boot? Sorry for the confusing. The issue is when we disable hardcap before kernel boot up, after kernel bring up, any changes of _PPC will update scaling_max_freq properly. If we enable hardcap before kernel boot up, after kernel bring up, even we disable it, scaling_max_freq does not be updated to max frequency, the max frequency just up to the value when bring up. Review related codes I found the limit came from user_policy.max, means when we set user_policy.max to 1000MHZ when boot up, then any changes of _PPC could not enlarge the scaling_max_freq, I think this is not as expected? please advise. Thanks, Joe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists