Messages in this thread | | | Date | Fri, 2 Aug 2013 12:29:27 +0530 | Subject | Re: [Update][PATCH] cpufreq: Do not hold driver module references for additional policy CPUs | From | Viresh Kumar <> |
| |
On 2 August 2013 12:19, Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> wrote: > But lsmod shows 0 for the cpufreq driver right? (Note, your related_cpus > should have only 1 CPU each, for you to see 0. Else, you'll see a non-zero > value due to the very bug/inconsistency that Rafael is fixing in this > patch).
I have hacked the driver this way:
@@ -2114,10 +2114,16 @@ int cpufreq_register_driver(struct cpufreq_driver *driver_data) cpufreq_driver = driver_data; write_unlock_irqrestore(&cpufreq_driver_lock, flags);
+ printk(KERN_INFO "%s: Module refcount: %lu\n", __func__, + module_refcount(cpufreq_driver->owner)); + ret = subsys_interface_register(&cpufreq_interface); if (ret) goto err_null_driver;
And this gave me 1..
| |