From: Kyle Moffett <mrmacman_g4@mac.com>
To: george@mvista.com
Cc: Nicolas Mailhot <nicolas.mailhot@laposte.net>,
Thomas Gleixner <tglx@linutronix.de>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 00/21] hrtimer - High-resolution timer subsystem
Date: Wed, 14 Dec 2005 03:58:21 -0500 [thread overview]
Message-ID: <E3BB92B7-2723-45F9-B578-C4BD07834734@mac.com> (raw)
In-Reply-To: <439F5B91.4010903@mvista.com>
On Dec 13, 2005, at 18:38, George Anzinger wrote:
> I think that there is a miss understanding here. The kernel
> timers, at this time, do not know or care about daylight savings
> time. This is not really a clock set but a time zone change which
> does not intrude on the kernels notion of time (that being, more or
> less UTC).
One question I have right now is: How does the kernel treat time
slewing? Sometimes I might want to say: "The clock has continuous
error and measures 24hours and 2 seconds for every 24 hours of real
time", in which case the monotonic time should be slewed -2sec/
24hours. On the other hand, I might also want to say: "The clock has
fixed error and is 2 hours ahead cause some dummy messed up the
time", so I'm going to fix this over the next 2 weeks by slewing
backwards 1 hour per 7 days, in which case I do _not_ want the
monotonic time to be affected (I'm passing 2 days, not 1 day and 22
hours). How does the kernel handle this? I've never seen any good
description of the NTP and time-control APIs; if there is one out
there (that's not 42 pages of dry standard), I would love a link.
Cheers,
Kyle Moffett
--
If you don't believe that a case based on [nothing] could potentially
drag on in court for _years_, then you have no business playing with
the legal system at all.
-- Rob Landley
next prev parent reply other threads:[~2005-12-14 8:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 12:45 [patch 00/21] hrtimer - High-resolution timer subsystem Nicolas Mailhot
2005-12-13 23:38 ` George Anzinger
2005-12-14 8:58 ` Kyle Moffett [this message]
2005-12-14 10:03 ` Nicolas Mailhot
2005-12-15 1:11 ` George Anzinger
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 0:01 tglx
2005-12-06 17:32 ` Roman Zippel
2005-12-06 19:07 ` Ingo Molnar
2005-12-07 3:05 ` Roman Zippel
2005-12-08 5:18 ` Paul Jackson
2005-12-08 8:12 ` Ingo Molnar
2005-12-08 9:26 ` Ingo Molnar
2005-12-08 13:08 ` Roman Zippel
2005-12-08 15:36 ` Steven Rostedt
2005-12-06 22:10 ` Thomas Gleixner
2005-12-07 3:11 ` Roman Zippel
2005-12-06 22:28 ` Thomas Gleixner
2005-12-07 9:31 ` Andrew Morton
2005-12-07 10:11 ` Ingo Molnar
2005-12-07 10:20 ` Ingo Molnar
2005-12-07 10:23 ` Nick Piggin
2005-12-07 10:49 ` Ingo Molnar
2005-12-07 11:09 ` Nick Piggin
2005-12-07 11:33 ` Ingo Molnar
2005-12-07 11:40 ` Nick Piggin
2005-12-07 13:06 ` Roman Zippel
2005-12-07 12:40 ` Roman Zippel
2005-12-07 23:12 ` Nick Piggin
2005-12-07 12:18 ` Roman Zippel
2005-12-07 16:55 ` Ingo Molnar
2005-12-07 17:17 ` Roman Zippel
2005-12-07 17:57 ` Ingo Molnar
2005-12-07 18:18 ` Roman Zippel
2005-12-07 18:02 ` Paul Baxter
2005-12-09 17:23 ` Thomas Gleixner
2005-12-12 13:39 ` Roman Zippel
2005-12-12 16:42 ` Thomas Gleixner
2005-12-12 18:37 ` Thomas Gleixner
2005-12-13 1:25 ` George Anzinger
2005-12-13 9:18 ` Thomas Gleixner
2005-12-15 1:35 ` Roman Zippel
2005-12-15 2:29 ` George Anzinger
2005-12-19 14:56 ` Roman Zippel
2005-12-19 20:54 ` George Anzinger
2005-12-21 23:03 ` Roman Zippel
2005-12-22 4:30 ` George Anzinger
2005-12-14 20:48 ` Roman Zippel
2005-12-14 22:30 ` Thomas Gleixner
2005-12-15 0:55 ` George Anzinger
2005-12-15 14:18 ` Steven Rostedt
2005-12-19 14:50 ` Roman Zippel
2005-12-19 22:05 ` 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=E3BB92B7-2723-45F9-B578-C4BD07834734@mac.com \
--to=mrmacman_g4@mac.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.mailhot@laposte.net \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).