From: Thomas Gleixner <tglx@linutronix.de>
To: zengtao <prime.zeng@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] cputime: Fix timeval-->cputime conversion
Date: Thu, 28 Jan 2016 09:22:04 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1601280921250.3886@nanos> (raw)
In-Reply-To: <1453964546-111074-1-git-send-email-prime.zeng@huawei.com>
Cc'ing Arnd
On Thu, 28 Jan 2016, zengtao wrote:
> The structure:
> struct timeval {
> __kernel_time_t tv_sec; /* seconds */
> __kernel_suseconds_t tv_usec; /* microseconds */
> };
> both __kernel_time_t and __kernel_suseconds_t are short than u64
> when it is 32bit platform, so force u64 conversion here.
>
> Signed-off-by: zengtao <prime.zeng@huawei.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> include/asm-generic/cputime_nsecs.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/asm-generic/cputime_nsecs.h b/include/asm-generic/cputime_nsecs.h
> index 0419485..e2f7ff9 100644
> --- a/include/asm-generic/cputime_nsecs.h
> +++ b/include/asm-generic/cputime_nsecs.h
> @@ -91,7 +91,8 @@ static inline void cputime_to_timespec(const cputime_t ct, struct timespec *val)
> */
> static inline cputime_t timeval_to_cputime(const struct timeval *val)
> {
> - u64 ret = val->tv_sec * NSEC_PER_SEC + val->tv_usec * NSEC_PER_USEC;
> + u64 ret = (u64)val->tv_sec * NSEC_PER_SEC +
> + val->tv_usec * NSEC_PER_USEC;
> return (__force cputime_t) ret;
> }
> static inline void cputime_to_timeval(const cputime_t ct, struct timeval *val)
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2016-01-28 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 7:02 [PATCH] cputime: Fix timeval-->cputime conversion zengtao
2016-01-28 8:22 ` Thomas Gleixner [this message]
2016-01-28 11:52 ` Arnd Bergmann
2016-01-29 3:12 ` Zengtao (B)
2016-01-29 8:46 ` Arnd Bergmann
2016-01-30 2:31 ` Zengtao (B)
2016-02-01 3:51 ` Zengtao (B)
2016-02-01 8:43 ` Thomas Gleixner
2016-02-02 2:57 ` Zengtao (B)
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=alpine.DEB.2.11.1601280921250.3886@nanos \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=prime.zeng@huawei.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