From: Adrian Hunter <adrian.hunter@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH V3] perf: x86: Improve accuracy of perf/sched clock
Date: Tue, 01 Sep 2015 11:36:38 +0300 [thread overview]
Message-ID: <55E56396.3090708@intel.com> (raw)
In-Reply-To: <1440147918-22250-1-git-send-email-adrian.hunter@intel.com>
On 21/08/15 12:05, Adrian Hunter wrote:
> When TSC is stable perf/sched clock is based on it.
> However the conversion from cycles to nanoseconds
> is not as accurate as it could be. Because
> CYC2NS_SCALE_FACTOR is 10, the accuracy is +/- 1/2048
>
> The change is to calculate the maximum shift that
> results in a multiplier that is still a 32-bit number.
> For example all frequencies over 1 GHz will have
> a shift of 32, making the accuracy of the conversion
> +/- 1/(2^33). That is achieved by using the
> 'clocks_calc_mult_shift()' function.
>
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Ping?
> ---
>
>
> Changes in V3:
>
> Use clocks_calc_mult_shift() instead of open-coded
> calculation
>
> Changes in V2:
>
> Remove definition of CYC2NS_SCALE_FACTOR
> Amend comments
>
>
> arch/x86/kernel/tsc.c | 24 +++++++++++-------------
> 1 file changed, 11 insertions(+), 13 deletions(-)
>
> diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> index c8d52cb4cb6e..39ec3d07affd 100644
> --- a/arch/x86/kernel/tsc.c
> +++ b/arch/x86/kernel/tsc.c
> @@ -167,21 +167,20 @@ static void cyc2ns_write_end(int cpu, struct cyc2ns_data *data)
> * ns = cycles * cyc2ns_scale / SC
> *
> * And since SC is a constant power of two, we can convert the div
> - * into a shift.
> + * into a shift. The larger SC is, the more accurate the conversion, but
> + * cyc2ns_scale needs to be a 32-bit value so that 32-bit multiplication
> + * (64-bit result) can be used.
> *
> - * We can use khz divisor instead of mhz to keep a better precision, since
> - * cyc2ns_scale is limited to 10^6 * 2^10, which fits in 32 bits.
> + * We can use khz divisor instead of mhz to keep a better precision.
> * (mathieu.desnoyers@polymtl.ca)
> *
> * -johnstul@us.ibm.com "math is hard, lets go shopping!"
> */
>
> -#define CYC2NS_SCALE_FACTOR 10 /* 2^10, carefully chosen */
> -
> static void cyc2ns_data_init(struct cyc2ns_data *data)
> {
> data->cyc2ns_mul = 0;
> - data->cyc2ns_shift = CYC2NS_SCALE_FACTOR;
> + data->cyc2ns_shift = 0;
> data->cyc2ns_offset = 0;
> data->__count = 0;
> }
> @@ -215,14 +214,14 @@ static inline unsigned long long cycles_2_ns(unsigned long long cyc)
>
> if (likely(data == tail)) {
> ns = data->cyc2ns_offset;
> - ns += mul_u64_u32_shr(cyc, data->cyc2ns_mul, CYC2NS_SCALE_FACTOR);
> + ns += mul_u64_u32_shr(cyc, data->cyc2ns_mul, data->cyc2ns_shift);
> } else {
> data->__count++;
>
> barrier();
>
> ns = data->cyc2ns_offset;
> - ns += mul_u64_u32_shr(cyc, data->cyc2ns_mul, CYC2NS_SCALE_FACTOR);
> + ns += mul_u64_u32_shr(cyc, data->cyc2ns_mul, data->cyc2ns_shift);
>
> barrier();
>
> @@ -256,12 +255,11 @@ static void set_cyc2ns_scale(unsigned long cpu_khz, int cpu)
> * time function is continuous; see the comment near struct
> * cyc2ns_data.
> */
> - data->cyc2ns_mul =
> - DIV_ROUND_CLOSEST(NSEC_PER_MSEC << CYC2NS_SCALE_FACTOR,
> - cpu_khz);
> - data->cyc2ns_shift = CYC2NS_SCALE_FACTOR;
> + clocks_calc_mult_shift(&data->cyc2ns_mul, &data->cyc2ns_shift, cpu_khz,
> + NSEC_PER_MSEC, 0);
> +
> data->cyc2ns_offset = ns_now -
> - mul_u64_u32_shr(tsc_now, data->cyc2ns_mul, CYC2NS_SCALE_FACTOR);
> + mul_u64_u32_shr(tsc_now, data->cyc2ns_mul, data->cyc2ns_shift);
>
> cyc2ns_write_end(cpu, data);
>
>
next prev parent reply other threads:[~2015-09-01 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 21:14 [PATCH V2] perf: x86: Improve accuracy of perf/sched clock Adrian Hunter
2015-08-17 7:34 ` Adrian Hunter
2015-08-17 9:56 ` Peter Zijlstra
2015-08-20 19:31 ` Thomas Gleixner
2015-08-21 6:46 ` Adrian Hunter
2015-08-21 9:05 ` [PATCH V3] " Adrian Hunter
2015-09-01 8:36 ` Adrian Hunter [this message]
2015-09-01 8:57 ` Peter Zijlstra
2015-09-13 11:08 ` [tip:perf/core] perf/x86: " tip-bot for Adrian Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55E56396.3090708@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.