From: Thomas Gleixner <tglx@linutronix.de>
To: Heena Sirwani <heenasirwani@gmail.com>
Cc: linux-kernel@vger.kernel.org, john.stultz@linaro.org, arnd@arndb.de
Subject: Re: [PATCH v5] timekeeping: Added a function to return tv_sec portion of ktime_get_ts64()
Date: Sat, 25 Oct 2014 17:12:48 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1410251705550.5308@nanos> (raw)
In-Reply-To: <20141025123406.GA13128@heena.com>
On Sat, 25 Oct 2014, Heena Sirwani wrote:
> +time64_t ktime_get_seconds(void)
> +{
> + time64_t ts;
> + struct timekeeper *tk = &tk_core.timekeeper;
> + struct timespec64 tomono;
> + s32 nsec;
> + unsigned int seq;
> +
> + WARN_ON(timekeeping_suspended);
> +
> + do {
> + seq = read_seqcount_begin(&tk_core.seq);
> + ts = tk->xtime_sec;
> + nsec = (long)(tk->tkr.xtime_nsec >> tk->tkr.shift);
> + tomono = tk->wall_to_monotonic;
> +
> + } while (read_seqcount_retry(&tk_core.seq, seq));
> +
> + ts += tomono.tv_sec;
> + if (nsec + tomono.tv_nsec >= NSEC_PER_SEC)
> + ts += 1;
> + return ts;
I'd rather have an extra field in the timekeeper
u64 xtime_sec;
+ u64 ktime_sec;
and update this in tk_update_ktime_data() so the readout function
boils down to
time64_t ktime_get_seconds(void)
{
#if BITS_PER_LONG < 64
u64 sec;
int seq;
do {
seq = read_seqcount_begin(&tk_core.seq);
sec = tk->ktime_sec;
} while (read_seqcount_retry(&tk_core.seq, seq));
return sec;
#else
return tk->ktime_sec;
#endif
}
So 64bit can do w/o the seqcount and 32bit avoids all extra math, right?
Thanks,
tglx
next prev parent reply other threads:[~2014-10-25 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 12:34 Heena Sirwani
2014-10-25 15:12 ` Thomas Gleixner [this message]
2014-10-25 15:22 ` Thomas Gleixner
2014-10-25 15:39 ` Arnd Bergmann
2014-10-25 17:32 ` Thomas Gleixner
2014-10-26 20:34 ` Arnd Bergmann
2014-10-28 11:26 ` Thomas Gleixner
2014-10-28 13:21 ` Arnd Bergmann
2014-10-26 21:01 ` Arnd Bergmann
2014-10-27 21:21 ` Thomas Gleixner
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.1410251705550.5308@nanos \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=heenasirwani@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®