From: David Daney <ddaney@caviumnetworks.com>
To: Wu Zhangin <wuzhangjin@gmail.com>
Cc: "Ralf Baechle" <ralf@linux-mips.org>,
linux-mips@linux-mips.org, "Ralf Rösch" <roesch.ralf@web.de>
Subject: Re: [PATCH v2 1/3] MIPS: add a common mips_cyc2ns()
Date: Wed, 07 Apr 2010 09:50:52 -0700 [thread overview]
Message-ID: <4BBCB7EC.5020403@caviumnetworks.com> (raw)
In-Reply-To: <9e1889ed5fa23dfaa1ad432ebb4b8f837f6668b4.1270655886.git.wuzhangjin@gmail.com>
On 04/07/2010 09:05 AM, Wu Zhangin wrote:
> From: Wu Zhangjin<wuzhangjin@gmail.com>
>
> Changes:
>
> v1 -> v2:
>
> o change the old mips_sched_clock() to mips_cyc2ns() and modify the
> arguments to support 32bit.
> o add 32bit support: use a smaller shift to avoid the quick overflow
> of 64bit arithmatic and balance the overhead of the 128bit arithmatic
> and the precision lost with the smaller shift.
>
> ----------------------
>
> Because the high resolution sched_clock() for r4k has the same overflow
> problem and solution mentioned in "MIPS: Octeon: Use non-overflowing
> arithmetic in sched_clock".
>
> "With typical mult and shift values, the calculation for Octeon's
> sched_clock overflows when using 64-bit arithmetic. Use 128-bit
> calculations instead."
>
> To reduce the duplication, This patch abstracts the solution into an
> inline funciton mips_cyc2ns() into arch/mips/include/asm/time.h from
> arch/mips/cavium-octeon/csrc-octeon.c.
>
> Two patches for Cavium and R4K will be sent out respectively to use this
> common function.
>
> Signed-off-by: Wu Zhangjin<wuzhangjin@gmail.com>
> ---
> arch/mips/include/asm/time.h | 38 ++++++++++++++++++++++++++++++++++++++
> 1 files changed, 38 insertions(+), 0 deletions(-)
>
> diff --git a/arch/mips/include/asm/time.h b/arch/mips/include/asm/time.h
> index c7f1bfe..898f0e0 100644
> --- a/arch/mips/include/asm/time.h
> +++ b/arch/mips/include/asm/time.h
> @@ -96,4 +96,42 @@ static inline void clockevent_set_clock(struct clock_event_device *cd,
> clockevents_calc_mult_shift(cd, clock, 4);
> }
>
> +static inline unsigned long long mips_cyc2ns(u64 cyc, u64 mult, u64 shift)
> +{
> +#ifdef CONFIG_32BIT
> + /*
> + * To balance the overhead of 128bit-arithematic and the precision
> + * lost, we choose a smaller shift to avoid the quick overflow as the
> + * X86& ARM does. please refer to arch/x86/kernel/tsc.c and
> + * arch/arm/plat-orion/time.c
> + */
> + return (cyc * mult)>> shift;
Have you tested that on a 32-bit kernel? I think it may overflow for
many cases.
David Daney
next prev parent reply other threads:[~2010-04-07 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 16:05 [PATCH v2 0/3] add high resolution sched_clock() for MIPS Wu Zhangin
[not found] ` <cover.1270655886.git.wuzhangjin@gmail.com>
2010-04-07 16:05 ` [PATCH v2 1/3] MIPS: add a common mips_cyc2ns() Wu Zhangin
2010-04-07 16:48 ` David Daney
2010-04-08 9:36 ` Wu Zhangjin
2010-04-07 16:50 ` David Daney [this message]
2010-04-08 9:32 ` Wu Zhangjin
2010-04-10 5:46 ` Wu Zhangjin
2010-04-07 16:05 ` [PATCH v2 2/3] MIPS: cavium-octeon: rewrite the sched_clock() based on mips_cyc2ns() Wu Zhangin
2010-07-29 1:24 ` wu zhangjin
2010-07-29 1:24 ` wu zhangjin
2010-04-07 16:05 ` [PATCH v2 3/3] MIPS: r4k: Add a high resolution sched_clock() Wu Zhangin
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=4BBCB7EC.5020403@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=roesch.ralf@web.de \
--cc=wuzhangjin@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox