From: Jan Kiszka <jan.kiszka@domain.hid>
To: Roderik_Wildenburg@domain.hid
Cc: Xenomai-help@domain.hid
Subject: Re: AW: [Xenomai-help] pthread_make_periodic_np and clock_gettime
Date: Thu, 15 Feb 2007 10:00:32 +0100 [thread overview]
Message-ID: <45D42130.80609@domain.hid> (raw)
In-Reply-To: <5D63919D95F87E4D9D34FF7748CE2C2A82C5D7@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]
Roderik_Wildenburg@domain.hid wrote:
> Sorry for the stupid question but: what is tick_arg ? Do I have to configure it within Xenomai or is it a kernel parameter ?
tick_arg is a nucleus module parameter, overloading
CONFIG_XENO_OPT_TIMING_PERIOD which requires XENO_OPT_TIMING_PERIODIC.
What setup do you have?
My problem was that I accidentally started the kernel at tick_arg=1000
(1 us), which didn't caused a locked up system because I ran it in qemu.
Just the tick conversion routines got confused. On a real target, you
will not be able to use such a system at all.
> The timing of my target in principal is fine. When I set
> tstart.tv_sec=0;
> tstart.tv_nsec=0;
> both to zero, my task gets peiodic (task runs every second). Just when using clock_gettime(CLOCK_REALTIME,&tstart) I get into trouble.
>
> Roderik
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: jan.kiszka@domain.hid [mailto:jan.kiszka@domain.hid
>> Gesendet: Mittwoch, 14. Februar 2007 18:44
>> An: Gilles Chanteperdrix
>> Cc: Wildenburg, Roderik RAEK3 MRA; Xenomai-help@domain.hid
>> Betreff: Re: [Xenomai-help] pthread_make_periodic_np and clock_gettime
>>
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>> > Roderik_Wildenburg@domain.hid wrote:
>>> > > Can anybody tell me, how I have to set the 2.
>> parameter (starttp)
>>> of > > pthread_make_periodic_np ?
>>> > > When I use clock_gettime to fill startp I get a giant timeout
>>> value in > > the /proc/xenomai/sched list and my task
>> never gets periodic.
>>> > >
>>> > > Is this just a problem of my hardware(PPC)/xenomai(2.3)
>>> combination or > > does anybody else have the same problem.
>>> > >
>>> > > See attached code example for easier testing.
>>> > >
>>> >
>>> > Confirmed over v2.3.x in periodic mode, aperiodic is
>> fine. Gilles?
>>> Ok. I will have a look at it.
>>>
>> Hmm, something went wrong here. I think I passed a too fast
>> tick_arg to the kernel yesterday which smashed the timing.
>> I'm now running the pperiodic demo at tick_arg=1000000 successfully.
>>
>> So, Roderik, either you did some similar mistake, or it's a PPC issue.
>>
>> Jan
>>
>>
>
> MAN Roland Druckmaschinen AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-02-15 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 6:58 AW: [Xenomai-help] pthread_make_periodic_np and clock_gettime Roderik_Wildenburg
2007-02-15 9:00 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-14 8:17 Roderik_Wildenburg
2007-02-14 8:53 ` Jan Kiszka
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=45D42130.80609@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Roderik_Wildenburg@domain.hid \
--cc=Xenomai-help@domain.hid \
/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.