All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Haberler <mail17@mah.priv.at>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] kconfig CONFIG_XENO_OPT_TIMING_PERIODIC=y/n
Date: Sun, 14 Apr 2013 07:54:31 +0200	[thread overview]
Message-ID: <516A4497.9010801@xenomai.org> (raw)
In-Reply-To: <3B6652EE-A4C6-4819-B3BB-DB02EFA1B08B@mah.priv.at>

On 01/29/2013 01:54 PM, Michael Haberler wrote:

> I'm testing linuxcnc with John's 3.5.7 - 2.6.2.1 kernel and found an
> issue with the deprecated linuxcnc xenomai-kernel threads version
> (the userland threads version is fine; both using native skin). I
> traced that back to rt_timer_ticks2ns(30000) returning zero.


Hi Michael,

I am unable to reproduce this issue. I have written the following 
kernel code:

#include <native/timer.h>

int init(void)
{
	rt_timer_set_mode(0);
	xnprintf("mode aperiodic, ticks2ns: %Lu\n", rt_timer_ticks2ns(30000));
	rt_timer_set_mode(1000000);
	xnprintf("mode periodic, ticks2ns: %Lu\n", rt_timer_ticks2ns(30000));
			
	return 0;
}

module_init(init);
MODULE_LICENSE("GPL");

And I get:
[   17.366373] Xenomai: mode 0, ticks2ns: 30000                                    
[   17.370918] Xenomai: mode periodic, ticks2ns: 30000000000                       

Which is the expected behaviour.

Could you send us a test case allowing to reproduce the issue you 
encountered ?


-- 
                                                                Gilles.


  parent reply	other threads:[~2013-04-14  5:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 12:54 [Xenomai] kconfig CONFIG_XENO_OPT_TIMING_PERIODIC=y/n Michael Haberler
2013-02-02 20:19 ` John Morris
     [not found]   ` <510D8568.6080406@xenomai.org>
2013-02-02 21:31     ` Gilles Chanteperdrix
2013-04-14  5:54 ` Gilles Chanteperdrix [this message]
2013-04-14  8:42   ` Michael Haberler

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=516A4497.9010801@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=mail17@mah.priv.at \
    --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.