All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Schlägl Manfred jun." <manfred.schlaegl@domain.hid>
To: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Adeos/Xenomai Arm Port
Date: Sat, 21 Oct 2006 14:11:53 +0200	[thread overview]
Message-ID: <1161432713.5007.16.camel@domain.hid> (raw)
In-Reply-To: <453647E6.2050307@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Hi!

One problem I had was that I needet to set very high periode-values for
latency and switchbench.
I think I've found a solution.

1. I increased the granularity of the system-timer
I'm using full system-clock für the timer now, instead of
system-clock/64 so now I have 1769472 ticks per jiffy (instead of 27648)

2. There was a wrong value for CLOCK_TICK_RATE in timex.h I think.
It was set to 50000000 / 16 (by netsilicon), but it should be the hw
clock frequency (http://arm.nihilisme.ca/doc/aleph.pdf )
CLOCK_TICK_RATE is now set to 176947200.

Results:
I'm able to pass Periods about 200us and lower to latency and
switchbench now.



But the Problem with Latency-Test with in-kernel periodic tasks and
in-kernel timer handler exists further.

ioctl RTTST_RTIOC_INTERM_BENCH_RES is sent once in userspace
and received twice (by rt_tmbench_ioctl_rt and
rt_tmbench_ioctl_nrt) ... 
There is no such behavior on my x86 running these tests.

Now i'll try to check the communication between the rt-driver and the
userspace now and will report my results.


Greets
	Manfred



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-10-21 12:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:16 [Xenomai-help] Adeos/Xenomai Arm Port Schlägl Manfred jun.
2006-10-18 15:27 ` Jan Kiszka
2006-10-18 15:56   ` Schlägl Manfred jun.
2006-10-19  5:52     ` Jan Kiszka
2006-10-21 12:11   ` Schlägl Manfred jun. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17 15:39 Schlägl Manfred jun.
2006-10-18  7:52 ` Schlägl Manfred jun.
2006-10-18 10:35   ` Jan Kiszka
2006-10-18 12:24     ` Schlägl Manfred jun.
2006-10-18 12:33       ` Jan Kiszka
2006-10-18 12:48         ` Gilles Chanteperdrix
2006-10-21 14:56       ` Schlägl Manfred jun.
2006-10-21 16:44         ` Jan Kiszka
2006-10-25  8:03           ` Schlägl Manfred jun.
2006-10-18 10:25 ` Philippe Gerum
2006-10-18 12:05   ` Gilles Chanteperdrix
2006-10-17  9:23 Schlägl Manfred jun.
2006-10-17  9:37 ` Jan Kiszka
2006-10-16 15:48 Schlägl Manfred jun.
2006-10-16 16:24 ` Jan Kiszka
2006-10-16 18:20 ` Gilles Chanteperdrix
2006-10-16 21:30 ` Philippe Gerum
2006-10-17  8:15   ` Gilles Chanteperdrix
2006-10-17  8:38     ` Gilles Chanteperdrix
2006-10-17  9:54       ` Philippe Gerum
2006-10-17 10:04     ` Philippe Gerum
2006-10-17 12:05       ` Gilles Chanteperdrix

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=1161432713.5007.16.camel@domain.hid \
    --to=manfred.schlaegl@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.