From: "Fleischer, Julie N" <julie.n.fleischer@intel.com>
To: "'george anzinger'" <george@mvista.com>,
"Fleischer, Julie N" <julie.n.fleischer@intel.com>,
high-res-timers-discourse@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: RE: Running POSIX Timers tests against HRT implementation
Date: Fri, 22 Nov 2002 11:55:41 -0800 [thread overview]
Message-ID: <D9223EB959A5D511A98F00508B68C20C0CCC1F80@orsmsx108.jf.intel.com> (raw)
> george anzinger wrote:
> Now, as to this particular issue, the 1003.1b-1993 standard
> in paragraph 14.2.1.2 says "The effect of setting a clock
> via clock_settime() on armed per process timers associated
> with that clock is implementation defined."
I see. Since I'm writing tests towards the 1003.1-2001 standards, I'll need
to be careful where there's a difference between that one and 1003.1b-1993,
as is the case with this issue. (If you'd still appreciate knowing the
deltas, I can still let you know when there is a difference in the
1003.1-2001 standard and the current implementation.)
In the 1003.1-2001 standards, it actually adds the qualifier that the line
you quoted applies to non-CLOCK_REALTIME clocks. If I'm interpreting that
standard correctly, CLOCK_REALTIME clocks should require that absolute
timers use the latest value of the clock and not behave relatively.
I'll make sure that I check the 1003.1b-1993 standards as well, though, when
reporting future issues.
- Julie
**These views are not necessarily those of my employer.**
next reply other threads:[~2002-11-22 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 19:55 Fleischer, Julie N [this message]
2002-11-22 20:26 ` Dan Kegel
2002-11-22 20:32 ` george anzinger
[not found] <D9223EB959A5D511A98F00508B68C20C0CCC1F7D@orsmsx108.jf.intel.com>
2002-11-22 19:01 ` george anzinger
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=D9223EB959A5D511A98F00508B68C20C0CCC1F80@orsmsx108.jf.intel.com \
--to=julie.n.fleischer@intel.com \
--cc=george@mvista.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--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®