From: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Heena Sirwani
<heenasirwani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
y2038-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] cpuset: Replace all instances of time_t with time64_t
Date: Wed, 25 Nov 2015 18:35:42 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1511251834550.12555@nanos> (raw)
In-Reply-To: <2798266.9VZu01a7d1@wuerfel>
On Wed, 25 Nov 2015, Arnd Bergmann wrote:
> The following patch replaces all instances of time_t with time64_t i.e.
> change the type used for representing time from 32-bit to 64-bit. All
> 32-bit kernels to date use a signed 32-bit time_t type, which can only
> represent time until January 2038. Since embedded systems running 32-bit
> Linux are going to survive beyond that date, we have to change all
> current uses, in a backwards compatible way.
>
> The patch also changes the function get_seconds() that returns a 32-bit
> integer to ktime_get_seconds() that returns seconds as 64-bit integer.
>
> The patch changes the type of ticks from time_t to u32. We keep ticks as
> 32-bits as the function uses 32-bit arithmetic which would prove less
> expensive than 64-bit arithmetic and the function is expected to be
> called atleast once every 32 seconds.
>
> Signed-off-by: Heena Sirwani <heenasirwani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Reviewed-by: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
> Signed-off-by: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
> ---
> This is an older patch I still had in my queue. Who should pick it up?
Tejun, Cc'ed
> diff --git a/kernel/cpuset.c b/kernel/cpuset.c
> index 10ae73611d80..c9ea63ff70a7 100644
> --- a/kernel/cpuset.c
> +++ b/kernel/cpuset.c
> @@ -51,6 +51,7 @@
> #include <linux/stat.h>
> #include <linux/string.h>
> #include <linux/time.h>
> +#include <linux/time64.h>
> #include <linux/backing-dev.h>
> #include <linux/sort.h>
>
> @@ -68,7 +69,7 @@ struct static_key cpusets_enabled_key __read_mostly = STATIC_KEY_INIT_FALSE;
> struct fmeter {
> int cnt; /* unprocessed events count */
> int val; /* most recent output value */
> - time_t time; /* clock (secs) when val computed */
> + time64_t time; /* clock (secs) when val computed */
> spinlock_t lock; /* guards read or write of above */
> };
>
> @@ -1374,7 +1375,7 @@ out:
> */
>
> #define FM_COEF 933 /* coefficient for half-life of 10 secs */
> -#define FM_MAXTICKS ((time_t)99) /* useless computing more ticks than this */
> +#define FM_MAXTICKS ((u32)99) /* useless computing more ticks than this */
> #define FM_MAXCNT 1000000 /* limit cnt to avoid overflow */
> #define FM_SCALE 1000 /* faux fixed point scale */
>
> @@ -1390,8 +1391,11 @@ static void fmeter_init(struct fmeter *fmp)
> /* Internal meter update - process cnt events and update value */
> static void fmeter_update(struct fmeter *fmp)
> {
> - time_t now = get_seconds();
> - time_t ticks = now - fmp->time;
> + time64_t now;
> + u32 ticks;
> +
> + now = ktime_get_seconds();
> + ticks = now - fmp->time;
>
> if (ticks == 0)
> return;
>
>
next prev parent reply other threads:[~2015-11-25 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:16 [PATCH] cpuset: Replace all instances of time_t with time64_t Arnd Bergmann
2015-11-25 17:35 ` Thomas Gleixner [this message]
2015-11-25 19:01 ` Tejun Heo
[not found] ` <20151125190150.GA14240-piEFEHQLUPpN0TnZuCh8vA@public.gmane.org>
2015-11-26 12:08 ` Zefan Li
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.1511251834550.12555@nanos \
--to=tglx-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=heenasirwani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=y2038-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
/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