From: John Stultz <john.stultz@linaro.org>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
xen-devel@lists.xen.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 2/4] time: add a notifier chain for when the system time is stepped
Date: Mon, 24 Jun 2013 10:50:07 -0700 [thread overview]
Message-ID: <51C886CF.4010001@linaro.org> (raw)
In-Reply-To: <51C87B26.3010904@citrix.com>
On 06/24/2013 10:00 AM, David Vrabel wrote:
> On 24/06/13 17:30, Thomas Gleixner wrote:
>> @@ -508,7 +509,7 @@ int do_settimeofday(const struct timespec *tv)
>>
>> tk_set_xtime(tk, tv);
>>
>> - timekeeping_update(tk, true, true);
>> + timekeeping_update(tk, true, true, true);
> These three booleans in a row is getting a bit opaque. How about I also
> change it to a set of flags? e.g.,
>
> timekeeping_updated(tk, TK_CLEAR_NTP | TK_MIRROR | TK_CLOCK_WAS_SET);
Yea. I'm not a fan of the bool arguments to functions (which I have to
look up every time as which bool is which).
The bitflag approach is nicer in my mind, since its a bit more explicit
when reading the code.
The other approach would be to have different function calls
(timekeeping_clear_ntp, timekeeping_mirror, timekeeping_clock_was_set),
which call into the same back end logic.
thanks
-john
next prev parent reply other threads:[~2013-06-24 17:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 19:16 [PATCHv5 0/4] xen: maintain an accurate persistent clock in more cases David Vrabel
2013-06-20 19:16 ` [PATCH 1/4] hrtimers: provide a hrtimers_late_resume() call David Vrabel
2013-06-20 19:16 ` David Vrabel
2013-06-21 7:53 ` Thomas Gleixner
2013-06-21 7:53 ` Thomas Gleixner
2013-06-21 12:32 ` David Vrabel
2013-06-21 12:32 ` David Vrabel
2013-06-21 14:32 ` Thomas Gleixner
2013-06-21 14:32 ` Thomas Gleixner
2013-06-21 17:30 ` David Vrabel
2013-06-21 21:24 ` Thomas Gleixner
2013-06-21 21:24 ` Thomas Gleixner
2013-06-21 17:30 ` David Vrabel
2013-06-20 19:16 ` [PATCH 2/4] time: add a notifier chain for when the system time is stepped David Vrabel
2013-06-20 19:16 ` David Vrabel
2013-06-21 7:57 ` Thomas Gleixner
2013-06-21 12:41 ` David Vrabel
2013-06-21 12:41 ` David Vrabel
2013-06-21 23:06 ` Thomas Gleixner
2013-06-21 23:06 ` Thomas Gleixner
2013-06-24 10:51 ` David Vrabel
2013-06-24 10:51 ` David Vrabel
2013-06-24 16:30 ` Thomas Gleixner
2013-06-24 16:30 ` Thomas Gleixner
2013-06-24 17:00 ` David Vrabel
2013-06-24 17:00 ` David Vrabel
2013-06-24 17:50 ` John Stultz
2013-06-24 17:50 ` John Stultz [this message]
2013-06-24 19:55 ` Thomas Gleixner
2013-06-24 19:55 ` Thomas Gleixner
2013-06-21 16:22 ` John Stultz
2013-06-21 16:22 ` John Stultz
2013-06-21 7:57 ` Thomas Gleixner
2013-06-20 19:16 ` [PATCH 3/4] x86/xen: sync the wallclock " David Vrabel
2013-06-20 19:16 ` David Vrabel
2013-06-20 19:16 ` [PATCH 4/4] x86/xen: sync the CMOS RTC as well as the Xen wallclock David Vrabel
2013-06-20 19:16 ` David Vrabel
2013-06-20 20:03 ` [PATCHv5 0/4] xen: maintain an accurate persistent clock in more cases John Stultz
2013-06-21 18:31 ` Konrad Rzeszutek Wilk
2013-06-21 18:31 ` Konrad Rzeszutek Wilk
2013-06-20 20:03 ` John Stultz
-- strict thread matches above, loose matches on Subject: below --
2013-06-19 15:25 [PATCHv4 " David Vrabel
2013-06-19 15:25 ` [PATCH 2/4] time: add a notifier chain for when the system time is stepped David Vrabel
2013-06-19 15:25 ` David Vrabel
2013-06-19 16:52 ` John Stultz
2013-06-19 16:52 ` John Stultz
2013-06-19 17:13 ` Konrad Rzeszutek Wilk
2013-06-19 17:13 ` Konrad Rzeszutek Wilk
2013-06-19 17:38 ` John Stultz
2013-06-19 17:38 ` John Stultz
2013-06-20 10:50 ` David Vrabel
2013-06-20 10:50 ` David Vrabel
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=51C886CF.4010001@linaro.org \
--to=john.stultz@linaro.org \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xen.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 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.