Re: [PATCH v2] cpufreq: stats: Add 'load_table' debugfs file to showaccumulated data of CPUs

From: Viresh Kumar
Date: Thu Jun 20 2013 - 11:43:01 EST

On 20 June 2013 16:48, Chanwoo Choi <cw00.choi@xxxxxxxxxxx> wrote:
> But,
> To show old frequency/new frequency on load_table debugfs file,
> governor function(dbs_check_cpu()) pass calculated CPUs load to specific governor(e.g., ondemand)
> as below function flow.
> dbs_check_cpu() (in cpufreq.c)
> -> od_check_cpu() (in cpufreq_ondemand.c)
> -> __cpufreq_driver_target() (in cpufreq.c)
> -> cpufreq_driver->target(policy)
> Also, The __cpufreq_driver_target() is external function which can be called on other file
> so I must consider exception case.
> If send CPUFREQ_LOADCHECK noti after changed cpu frequency,
> I think it is complicated and has quite a little difficulty.
> What is your opinion?

What you can do is:
- create another routine: cpufreq_governor_driver_target()
- replace all __cpufreq_driver_target() from ondemand/conservative governors
with this one
- In cpufreq_governor_driver_target() call __cpufreq_driver_target() and
take a note of new freq.

Maybe you don't need to check the actual freq that is set (even
that would be simple to implement), but what is requested.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at