[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpomx54Y3WVToYP0nOw-hsxKzGjp2nyfzWf5bo1s530Yg1w@mail.gmail.com>
Date: Thu, 20 Jun 2013 16:25:31 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Chanwoo Choi <cw00.choi@...sung.com>
Cc: rjw@...k.pl, linux-kernel@...r.kernel.org,
Kyungmin Park <kyungmin.park@...sung.com>,
Myungjoo Ham <myungjoo.ham@...sung.com>
Subject: Re: [PATCH v2] cpufreq: stats: Add 'load_table' debugfs file to show
accumulated data of CPUs
On 20 June 2013 16:15, Chanwoo Choi <cw00.choi@...sung.com> wrote:
> Yes, freq->old is same freq->new.
>
> The cpufreq gorvernor(dbs_check_cpu()) send CPUFREQ_LOADCHECK noti
> right after calculating CPUs load, regardless of changing CPU frequency.
> So, I use only freq->old value without using freq->new because load_table
> debugfs file need current cpu frequency.
>
> Now, I can't think of any proper usage for freq->new.
> Do you have good way for using freq->new to include more useful data in load_table?
This information might be interesting.. At what load, we moved from
which freq to which one..
Just see if you can add the notification after frequency has been
changed.
--
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