From: Wolfgang Mauerer <wolfgang.mauerer@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "Kiszka, Jan" <jan.kiszka@domain.hid>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH 0/7] Host realtime clock support
Date: Sat, 03 Jul 2010 21:29:31 +0200 [thread overview]
Message-ID: <4C2F8F9B.30300@domain.hid> (raw)
In-Reply-To: <4C2F6BCA.2020300@domain.hid>
Gilles Chanteperdrix wrote:
> Wolfgang Mauerer wrote:
>> Some points that may require further discussion:
>>
>> - POSIX only specifies a few clock_ids, and these have already been
>> extended by the Linux kernel. We use the maximum id (16) for the new
>> clock, but it might also make sense to use 7 (CLOCK_MONOTONIC_COARSE+1)
>> or 4 (CLOCK_THREAD_CPUTIME_ID+1).
>
> Why are we limited to 16 clocks? I mean we do not go trough any
> kernel/glibc path, so it looks like we can use any number. Or did I miss
> something?
>
To goal was to find a number that's least surprising and blends best
with the POSIX conventions and the existing numbers in Linux. Maximum
was referring to the definition in the Linux kernel, but I'm happy
to pick any larger number, including 23 and 42 ;-)
Regards, Wolfgang
prev parent reply other threads:[~2010-07-03 19:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 11:49 [Xenomai-core] [PATCH 0/7] Host realtime clock support Wolfgang Mauerer
2010-07-02 11:49 ` [Xenomai-core] [PATCH 1/7] nucleus: Spelling fix for check-vdso.c Wolfgang Mauerer
2010-07-02 11:49 ` [Xenomai-core] [PATCH 2/7] nucleus: Sanity check for vdso.h Wolfgang Mauerer
2010-07-02 11:49 ` [Xenomai-core] [PATCH 3/7] nucleus: Add userland cpu_relax() definition for x86 Wolfgang Mauerer
2010-07-02 11:49 ` [Xenomai-core] [PATCH 4/7] nucleus: Add CLOCK_HOST_REALTIME bits to nkvdso Wolfgang Mauerer
2010-07-03 11:57 ` Gilles Chanteperdrix
2010-07-03 19:31 ` Wolfgang Mauerer
2010-07-03 19:52 ` Gilles Chanteperdrix
2010-07-03 20:25 ` Wolfgang Mauerer
2010-07-02 11:49 ` [Xenomai-core] [PATCH 5/7] posix: Support reading the host realtime clock in realtime context Wolfgang Mauerer
2010-07-03 12:04 ` Gilles Chanteperdrix
2010-07-03 19:21 ` Wolfgang Mauerer
2010-07-02 11:49 ` [Xenomai-core] [PATCH 6/7] posix: Userspace hostrt reading without switching to kernel mode Wolfgang Mauerer
2010-07-03 12:06 ` Gilles Chanteperdrix
2010-07-02 11:49 ` [Xenomai-core] [PATCH 7/7] posix: Add some example code for CLOCK_HOST_REALTIME Wolfgang Mauerer
2010-07-02 14:21 ` Jan Kiszka
2010-07-02 14:26 ` Gilles Chanteperdrix
2010-07-02 14:34 ` Wolfgang Mauerer
2010-07-02 14:35 ` Gilles Chanteperdrix
2010-07-02 14:39 ` Jan Kiszka
2010-07-02 14:31 ` [Xenomai-core] [PATCH (7+1)/7] " Wolfgang Mauerer
2010-07-02 13:52 ` [Xenomai-core] [PATCH 0/7] Host realtime clock support Gilles Chanteperdrix
2010-07-02 14:59 ` Wolfgang Mauerer
2010-07-02 15:07 ` Gilles Chanteperdrix
2010-07-02 15:20 ` Jan Kiszka
2010-07-03 18:46 ` Wolfgang Mauerer
2010-07-03 16:56 ` Gilles Chanteperdrix
2010-07-03 19:29 ` Wolfgang Mauerer [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=4C2F8F9B.30300@domain.hid \
--to=wolfgang.mauerer@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.