All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "Mauerer, Wolfgang" <wolfgang.mauerer@domain.hid>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH 7/7] posix: Add some example code for	CLOCK_HOST_REALTIME
Date: Fri, 02 Jul 2010 16:39:02 +0200	[thread overview]
Message-ID: <4C2DFA06.1050001@domain.hid> (raw)
In-Reply-To: <4C2DF91B.5050202@domain.hid>

Gilles Chanteperdrix wrote:
> Wolfgang Mauerer wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>>> Wolfgang Mauerer wrote:
>>>>> ... and for reading the contents of the hostrt data.
>>>>>
>>>> Just realized: Please also update clocktest. Should already work with
>>>> the new clock ID, but requires a cosmetic output patch.
>>> Yes, I thought about that. Maybe even if clocktest uses the new
>>> clock_id, we could drop the example?
>>>
>>> I do not think it is a good idea to provide as an example code which
>>> uses the internals of the implementation (though it makes sense to use
>>> the implementation internals in the clocktest code). And if we remove
>>> that, only clock_gettime(CLOCK_HOST_REALTIME) remains, which does not
>>> seem to need an example.
>>>
>> I would not keep it as an example, but as a test case for checking that
>> nothing is wrong with the data on the shared page. Which does not fit
>> quite well into clocktest. Although I have no problem with just omitting
>> the stuff if reading the (internal) content of the data page is deemed
>> inappropriate.
> 
> Well, I see nothing wrong with checking the internals at the beginning
> of clocktest is the clockid passed to clocktest is CLOCK_HOST_REALTIME.
> But Jan may have another opinion, since he is the one who wrote this code.

If clock_gettime(CLOCK_HOST_REALTIME) succeeds, I don't think we need to
do anything special. But if it should fail, dumping a more detailed
reason based on those additional checks in the example would be helpful.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2010-07-02 14:39 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 [this message]
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

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=4C2DFA06.1050001@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=wolfgang.mauerer@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.