Re: [PATCH] Report CPU speed for TIMER based profiling too.

[Maynard J. <may...@us...>]

On 11/21/2011 3:57 AM, Joakim Tjernlund wrote:
> Seems a bit silly to report 0 MHz for all TIMER based profiling, move
Actually, current code (as of the s390 patch) does not print the clock speed 
unless it's greater than 0.  Nevertheless, I don't see any reason why we should 
not print actual clock speed when doing timer mode, so I accepted your patch, 
and it's committed upstream now.

Thanks.
-Maynard

> the calculation upwards to avoid that.
>
> Signed-off-by: Joakim Tjernlund<Joa...@tr...>
> ---
>   daemon/opd_events.c |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/daemon/opd_events.c b/daemon/opd_events.c
> index b544fb3..a49954d 100644
> --- a/daemon/opd_events.c
> +++ b/daemon/opd_events.c
> @@ -82,6 +82,8 @@ void opd_parse_events(char const * events)
>   	char * c;
>   	size_t cur = 0;
>
> +	cpu_speed = op_cpu_frequency();
> +
>   	if (cpu_type == CPU_TIMER_INT) {
>   		struct opd_event * event =&opd_events[0];
>   		event->name = xstrdup("TIMER");
> @@ -121,8 +123,6 @@ void opd_parse_events(char const * events)
>   	}
>
>   	free(ev);
> -
> -	cpu_speed = op_cpu_frequency();
>   }
>
>