linux-kernel - [PATCH 0/4] CPUFreq stats: Bug fixes

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: <cover.1380190886.git.viresh.kumar@linaro.org>
Date:	Thu, 26 Sep 2013 15:59:50 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	rjw@...k.pl
Cc:	linaro-kernel@...ts.linaro.org, patches@...aro.org,
	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org, srivatsa.bhat@...ux.vnet.ibm.com,
	nicolas.pitre@...aro.org, Viresh Kumar <viresh.kumar@...aro.org>
Subject: [PATCH 0/4] CPUFreq stats: Bug fixes

Hi Rafael,

I know you asked me not to send any more patches before the earlier ones get
into kernel. I got to this as Nicolas Pitre required to send few CPUFreq patches
for ARM's big LITTLE In-Kernel-Switcher. And within linaro we have hacked these
bugs in a bad way..

Because of his dependency I am forced to send these.. These aren't introduced
recently and so they can be included in 3.13.

There are several problems/bugs in cpufreq-stats specially with cpufreq drivers
as modules and suspend/resume path. These are mentioned well in changelogs.

These are tested over my thinkpad (acpi-cpufreq) in following way:
[1] offline+online all CPUs except boot cpu in a while loop
[2] then do suspend resume
[3] repeat [1] and [2] several times.

No issues found..

Also tested on my exynos board:
- Added cpufreq_unregister/register while loop in exynos-cpufreq.c so that we
  continuously register/unregister driver... Stats were working fine now..
- Compile cpufreq-stats as module and insert/remove it several times after
  removing above hack (as that doesn't let linux boot :) )..

@Srivatsa: You also have fairly good idea of cpufreq now, so please give some
time to review this :)

@Nico: Can you remove the hacky code from IKS tree and test these instead to see
if we still have any issues?

--
viresh

Viresh Kumar (4):
  cpufreq: stats: handle cpufreq_unregister_driver() and suspend/resume
    properly
  cpufreq: stats: remove hotplug notifiers
  cpufreq: stats: free table and remove sysfs entry in a single routine
  cpufreq: stats: create sysfs entries when cpufreq_stats is a module

 drivers/cpufreq/cpufreq.c       |   5 ++
 drivers/cpufreq/cpufreq_stats.c | 109 ++++++++++++++++++----------------------
 include/linux/cpufreq.h         |   2 +
 3 files changed, 55 insertions(+), 61 deletions(-)

-- 
1.7.12.rc2.18.g61b472e

--
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/