[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3966081.PYqoVoQ0Wq@vostro.rjw.lan>
Date: Mon, 24 Jun 2013 12:20:57 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Chanwoo Choi <cw00.choi@...sung.com>, 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 Monday, June 24, 2013 03:11:15 PM Viresh Kumar wrote:
> On 24 June 2013 15:09, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > On Monday, June 24, 2013 11:48:22 AM Viresh Kumar wrote:
> >> On 21 June 2013 18:43, Rafael J. Wysocki <rjw@...k.pl> wrote:
> >> > Well, to be honest, I don't like the whole thing. The more changes you need
> >> > to make to the common code to support it, the worse.
> >>
> >> You meant you didn't like this patch completely? Or the idea that
> >> I gave?
> >
> > Well, kind of both ...
> >
> >> Getting the new frequency would be very useful IMHO. That would
> >> give us a relation between old/new freq and load on each cpu at
> >> that time. That's why I suggested it.
> >
> > Where "us" is user space or what?
>
> User space as well as the developers who are accessing this information.
My impression was that that new interface wouldn't be useful on all platforms
supported by cpufreq. If that's the case, I'd rather not make changes in the
core code that are needed only to implement that new interface, at least to
start with.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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