From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: paulus@samba.org
Cc: akpm@osdl.org, ak@muc.de, clameter@engr.sgi.com,
linux-kernel@vger.kernel.org, ralf@linux-mips.org,
johnstul@us.ibm.com, rth@twiddle.net
Subject: Re: [PATCH] simplify update_times (avoid jiffies/jiffies_64 aliasing problem)
Date: Sun, 05 Mar 2006 01:43:38 +0900 (JST) [thread overview]
Message-ID: <20060305.014338.25910236.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <17417.35072.247188.486774@cargo.ozlabs.ibm.com>
>>>>> On Sat, 4 Mar 2006 23:33:04 +1100, Paul Mackerras <paulus@samba.org> said:
>> > > Also I assume Atsushi-san did the patch because he saw a real problem?
>> >
>> > Yes, one which I also saw on PPC. The compiler (gcc-4) emits loads
>> > for jiffies, jiffies64 and wall_jiffies before storing the incremented
>> > jiffies64 value back.
>> >
>>
>> What was the effect of that?
paulus> The effect is that the first call to do_timer doesn't increment xtime.
paulus> This explains why the code I have to detect disagreements between
paulus> xtime and the time of day as computed from the timebase register was
paulus> finding a disagreement on the first tick, which I was scratching my
paulus> head over.
paulus> There may be other effects on architectures which use wall_jiffies to
paulus> detect lost timer ticks. We don't have that problem on PPC and we
paulus> don't use wall_jiffies in computing time of day.
Well, I found this problem during investigating an another MIPS
do_gettimeofday() bug which was fixed recently. It was:
lost = jiffies - wall_jiffies;
...
} else if (unlikely(lost))
usecs += lost * tick_usec;
The tick_usec should not be used here since it is based on USER_HZ.
It is 'usecs += lost * (USECS_PER_SEC /HZ)' now.
I wondered why this bug really affects gettimeofday() always though
the 'lost' should usually be 0. And finally I noticed the
jiffies/jiffies_64 optimization issue.
---
Atsushi Nemoto
next prev parent reply other threads:[~2006-03-04 16:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 14:02 Atsushi Nemoto
2006-03-02 15:51 ` Atsushi Nemoto
2006-03-02 19:09 ` Christoph Lameter
2006-03-03 2:44 ` Atsushi Nemoto
2006-03-03 3:04 ` Andrew Morton
2006-03-03 3:20 ` Andi Kleen
2006-03-03 4:31 ` Atsushi Nemoto
2006-03-03 5:45 ` David S. Miller
2006-03-03 16:26 ` Atsushi Nemoto
2006-03-03 16:31 ` Atsushi Nemoto
2006-03-04 8:18 ` Andrew Morton
2006-03-04 11:20 ` Andi Kleen
2006-03-04 11:40 ` Andrew Morton
2006-03-04 5:21 ` Andi Kleen
2006-03-04 23:13 ` Paul Mackerras
2006-03-06 2:32 ` Atsushi Nemoto
2006-03-04 11:42 ` Paul Mackerras
2006-03-04 11:44 ` Andrew Morton
2006-03-04 12:33 ` Paul Mackerras
2006-03-04 16:43 ` Atsushi Nemoto [this message]
2006-03-03 20:17 ` john stultz
2006-03-03 21:15 ` Andrew Morton
2006-03-04 17:15 ` Atsushi Nemoto
2006-07-30 14:54 ` Atsushi Nemoto
2006-07-31 10:36 ` Martin Schwidefsky
2006-08-01 14:44 ` Atsushi Nemoto
2006-08-02 12:50 ` Martin Schwidefsky
2006-08-03 15:53 ` Atsushi Nemoto
2006-08-04 14:02 ` Martin Schwidefsky
2006-08-06 16:13 ` Atsushi Nemoto
2006-08-07 11:28 ` Martin Schwidefsky
2006-08-07 19:58 ` Andrew Morton
2006-08-08 8:11 ` Martin Schwidefsky
2006-08-09 15:07 ` Atsushi Nemoto
2006-03-03 18:13 ` john stultz
2006-03-04 2:34 ` Ralf Baechle
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=20060305.014338.25910236.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
/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®