> add window to show frequency stats for devfreq devices
>
> Signed-off-by: Rajagopal Venkat
> Signed-off-by: Sanjay Singh Rawat
> ---
>
> v4 - remove resizing before freeing the vector
>
> v3 - remove unused variables, reduce array size to suitable value
>- replace the inactive code block
On (09/30/14 12:04), Sanjay Singh Rawat wrote:
> add window to show frequency stats for devfreq devices
>
> Signed-off-by: Rajagopal Venkat
> Signed-off-by: Sanjay Singh Rawat
> ---
>
> v2 - Show devfreq window on support basis. Check for empty devfreq
> directory.
>- Free the open dir
gt; >> + void update_devfreq_freq_state(uint64_t freq, uint64_t time);
> >> + void parse_devfreq_trans_stat(char *dname);
> >> + void process_time_stamps();
> >> +
> >> +public:
> >> +
> >> + vector dstates;
> >> +
> >>
On (07/01/14 17:54), Amit Kucheria wrote:
> Date: Tue, 1 Jul 2014 17:54:15 +0530
> From: Amit Kucheria
> To: Mohammad Merajul Islam Molla ,
> power...@lists.01.org
> Cc: Lists linaro-dev
> Subject: Re: [Powertop] [PATCH POWERTOP] Fix various resource leaks
>
> Mohammad,
>
> This fix should go
On (06/04/14 11:27), Sanjay Singh Rawat wrote:
> bogomips is removed by timer-backed delay loop (commit 9fc2105a)
> in ARM kernel. Using other suitable string to decide to enumerate each
> cpu.
looks good.
-ss
> Signed-off-by: Sanjay Singh Rawat
> ---
> src/cpu/cpu.cpp | 12
On (12/04/12 11:37), Rajagopal Venkat wrote:
> Powertop fails to display frequency stats when cpuidle subsystem
> is not enabled. Fix it.
>
> Signed-off-by: Rajagopal Venkat
> ---
looks good to me, thanks.
-ss
> src/cpu/cpu.h | 7 ++-
> src/cpu/cpu_linux.cpp | 36 +++
On (09/28/12 09:54), Chris Ferron wrote:
[..]
> Well to be fair, not that I agree any-more, but years ago it was
> common practice to disable exceptions (via the compiler) for C++ in
> very specialized "REAL" "Embedded Systems". This practice was
> problematic in that you needed to have a will defi
On (09/27/12 00:09), Magnus Fromreide wrote:
> That they fail to throw exceptions from new is no reason to disable
> set_new_handler, the newhandler is called by the runtime on out of memory
> and is intended to allow the user to try fixing the issue. This is true for
> the noexcept version as well
Hi,
On (09/05/12 15:52), Rajagopal Venkat wrote:
> Incorrect timer and work perf events timestamp tracing is one
> of the reason for reporting usage over 100%. This patch will
> resolve the issue by
> - rejecting the events for which entry timestamp is not recorded.
how is that possible?
do you m
