From: Thomas Gleixner <tglx@linutronix.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Stefan Liebler <stli@linux.vnet.ibm.com>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: futex timeout not working? (bisected)
Date: Fri, 16 Oct 2015 14:45:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1510161443520.4212@nanos> (raw)
In-Reply-To: <alpine.DEB.2.11.1510161416050.4212@nanos>
Heiko,
On Fri, 16 Oct 2015, Thomas Gleixner wrote:
> On Fri, 16 Oct 2015, Heiko Carstens wrote:
> > Adding the patch below also "fixes" this. Right now I don't see why this
> > could architecture specific. Hmm.
> >
> > diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> > index 3739ac6aa473..75771b15647c 100644
> > --- a/kernel/time/timekeeping.c
> > +++ b/kernel/time/timekeeping.c
> > @@ -1835,7 +1835,7 @@ void update_wall_time(void)
> > * memcpy under the tk_core.seq against one before we start
> > * updating.
> > */
> > - timekeeping_update(tk, clock_set);
> > + timekeeping_update(tk, clock_set | TK_CLOCK_WAS_SET);
> > memcpy(real_tk, tk, sizeof(*tk));
> > /* The memcpy must come last. Do not put anything here! */
> > write_seqcount_end(&tk_core.seq);
>
> Well, the latter is incrementing the sequence count on every wall time
> update.
>
> The question is why the hrtimer code is not seeing that the clock was
> set at some point during boot.
>
> Lemme dig into that.
The only point I found which does not update the sequence count is
timekeeping_init().
Does the patch below fix your issue?
Thanks,
tglx
8<--------------------
diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
index 3739ac6aa473..44d2cc0436f4 100644
--- a/kernel/time/timekeeping.c
+++ b/kernel/time/timekeeping.c
@@ -1251,7 +1251,7 @@ void __init timekeeping_init(void)
set_normalized_timespec64(&tmp, -boot.tv_sec, -boot.tv_nsec);
tk_set_wall_to_mono(tk, tmp);
- timekeeping_update(tk, TK_MIRROR);
+ timekeeping_update(tk, TK_MIRROR | TK_CLOCK_WAS_SET);
write_seqcount_end(&tk_core.seq);
raw_spin_unlock_irqrestore(&timekeeper_lock, flags);
next prev parent reply other threads:[~2015-10-16 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 10:43 futex timeout not working? (bisected) Heiko Carstens
2015-10-16 10:21 ` Thomas Gleixner
2015-10-16 10:31 ` Heiko Carstens
2015-10-16 10:33 ` Thomas Gleixner
2015-10-16 10:38 ` Heiko Carstens
2015-10-16 10:35 ` Thomas Gleixner
2015-10-16 10:54 ` Heiko Carstens
2015-10-16 11:50 ` Heiko Carstens
2015-10-16 12:19 ` Thomas Gleixner
2015-10-16 12:45 ` Thomas Gleixner [this message]
2015-10-16 13:41 ` Heiko Carstens
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.1510161443520.4212@nanos \
--to=tglx@linutronix.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=stli@linux.vnet.ibm.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