From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: gettimeofday question
Date: Sat, 3 Mar 2001 12:49:04 +0000 (GMT) [thread overview]
Message-ID: <200103031249.f23Cn4R01208@flint.arm.linux.org.uk> (raw)
Hi,
I've noticed that one of my machines here suffers from the "time going
backwards problem" and so started thinking about the x86 solution.
I've come to the conclusion that it has a hole which could cause it
to return the wrong time in one specific case:
- in do_gettimeofday(), we disable irqs (read_lock_irqsave)
- the ISA timer wraps, but we've got interrupts disabled, so no update
of xtime or jiffies occurs
- in do_slow_gettimeoffset(), we read the timer, which has wrapped
- since jiffies_p != jiffies, we do not apply any correction
- our idea of time is now one jiffy slow.
Further more, while do_gettimeofday() is still within the
read_lock_irqsave, we spin_unlock(&i8253_lock) in do_slow_gettimeoffset()
and _re-enable_ interrupts! This means when we later read xtime, we're
doing it with interrupts enabled.
This applies to both 2.2.18 and 2.4.2.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2001-03-03 12:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 12:49 Russell King [this message]
2001-03-03 16:24 ` Russell King
2001-03-19 7:33 ` Russell King
2001-03-19 11:39 ` Jamie Lokier
2001-03-19 18:26 ` Eli Carter
2001-03-19 19:06 ` Russell King
2001-03-19 19:49 ` Eli Carter
2001-03-19 21:34 ` Russell King
2001-03-19 22:54 ` Eli Carter
2001-03-19 23:44 ` Russell King
2001-03-20 15:27 ` Eli Carter
2001-03-21 22:14 ` Eli Carter
2001-03-21 22:27 ` Eli Carter
2001-03-21 23:10 ` Eli Carter
2001-03-21 23:27 ` Question on binutils release to use Anthony Barbachan
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=200103031249.f23Cn4R01208@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--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®