From: George Anzinger <george@wildturkeyranch.net>
To: tglx@linutronix.de
Cc: Lee Revell <rlrevell@joe-job.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Clean up of hrtimer code.
Date: Thu, 19 Jan 2006 13:50:05 -0800 [thread overview]
Message-ID: <43D0098D.5080000@wildturkeyranch.net> (raw)
In-Reply-To: <1137704954.7947.65.camel@localhost.localdomain>
Thomas Gleixner wrote:
>George,
>
>On Thu, 2006-01-19 at 12:53 -0800, George Anzinger wrote:
>
>
>>>The assumption that the CLOCK_REALTIME/MONOTONIC relationship is valid
>>>for all additional clocks is not correct.
>>>
>>>
>>Well, it is until it isn't. There really does need to be a paring of some
>>sort to sort out the ABS flag.
>>
>>
>
>How is this applicable to some additional non posix clocks ? It applies
>to CLOCK_MONOTONIC and CLOCK_REALTIME, but nothing speaks against
>implementing CLOCK_WHATEVER with a totally different behaviour vs. the
>ABS_TIME flag. Am I missing something ?
>
>
>
How ever it is done the selection of a base depends on the mode and the
clock. I suggested mapping this via
odd/ even, but, I think what is needed is some way to code this into
hrtimer.c in a reasonable way. Your choice, really.
--
George Anzinger george@wildturkeyranch.net
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
prev parent reply other threads:[~2006-01-19 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 1:54 George Anzinger
2006-01-19 20:18 ` Thomas Gleixner
2006-01-19 20:53 ` George Anzinger
2006-01-19 21:09 ` Thomas Gleixner
2006-01-19 21:50 ` George Anzinger [this message]
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=43D0098D.5080000@wildturkeyranch.net \
--to=george@wildturkeyranch.net \
--cc=akpm@osdl.org \
--cc=george@mwildturkeyranch.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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®