From: Jan Kiszka <jan.kiszka@domain.hid>
To: "\"Schlägl \\\"Manfred jun.\\\"\"" <manfred.schlaegl@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Adeos/Xenomai Arm Port
Date: Wed, 18 Oct 2006 14:33:16 +0200 [thread overview]
Message-ID: <45361F0C.1010007@domain.hid> (raw)
In-Reply-To: <1161174276.5093.22.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 4089 bytes --]
Schlägl Manfred jun. wrote:
> On Wed, 2006-10-18 at 12:35 +0200, Jan Kiszka wrote:
>
>> I vote for solution 4:
>>
>> --- include/rtdm/rttesting.h (revision 1731)
>> +++ include/rtdm/rttesting.h (working copy)
>> @@ -85,8 +85,8 @@ typedef struct rttst_overall_bench_res {
>>
>> typedef struct rttst_tmbench_config {
>> int mode;
>> - nanosecs_rel_t period;
>> int priority;
>> + nanosecs_rel_t period;
>> int warmup_loops;
>> int histogram_size;
>> int histogram_bucketsize;
>>
>> Could you check if this helps?
>>
>> Thanks,
>> Jan
>>
>
>
> Thanks! It works. ioctls are working
Ok, I will apply the patch.
>
> But there is another Problem: I've inserted debug messages
>
> // USER-PROCESS
> -sh-3.00# ./run -- -t 1 -p 10000 -T 5
> *
> *
> * Type ^C to stop this application.
> *
> *
> Using /lib/modules/2.6.15.7/kernel/drivers/xenomai/testing/xeno_timerbench.ko
> == Sampling period: 10000 us
> == Test mode: in-kernel periodic task
> == All results in microseconds
> LATENCY: display send RTTST_RTIOC_TMBENCH_START:
> mode 0
> periode 1
> pri 99
> warmup 1
> hist_s 0
> hist_bs 1000
> fmax 0
> DEBUG: rt_dev_ioctl: request: 1075840528
> warming up...
> DEBUG: rt_dev_ioctl: request: -1070594560
> RTT| 00:00:01 (in-kernel periodic task, 10000 us period, priority 99)
> RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat
> worst
> RTD| 29.369| 32.341| 35.879| 0| 29.369|
> 35.879
> DEBUG: rt_dev_ioctl: request: -1070594560
> RTD| 22.135| 32.381| 36.241| 0| 22.135|
> 36.241
> DEBUG: rt_dev_ioctl: request: -1070594560
> RTD| 21.050| 32.378| 37.326| 0| 21.050|
> 37.326
> DEBUG: rt_dev_ioctl: request: -1070594560
> DEBUG: rt_dev_ioctl: request: -1071118831
> ---|------------|------------|------------|--------|-------------------------
> RTS|-1095770.696| 0.001| 93.660| 93748|
> 00:00:05/00:00:05
> -sh-3.00#
>
> // KERNEL-OUTPUT
>
> [42949410.980000] KERNEL: rt_tmbench_ioctl_nrt got request 1075840528
> [42949410.990000] KERNEL: rt_tmbench_ioctl_nrt got
> RTTST_RTIOC_TMBENCH_START:
> [42949411.020000] mode 0
> [42949411.020000] periode 10000000
> [42949411.030000] pri 99
> [42949411.040000] warmup 1
> [42949411.050000] hist_s 0
> [42949411.060000] hist_bs 1000
> [42949411.070000] fmax 0
> [42949411.080000] KERNEL: rt_tmbench_ioctl_nrt got request -1070594560
> [42949411.090000] rt_tmbench_ioctl_nrt: request
> -1070594560(RTTST_RTIOC_INTERM_BENCH_RES) -> ret = -ENOSYS(-38)
> [42949411.120000] rt_tmbench_ioctl_rt -1070594560
> [42949413.070000] KERNEL: rt_tmbench_ioctl_nrt got request -1070594560
> [42949413.090000] rt_tmbench_ioctl_nrt: request
> -1070594560(RTTST_RTIOC_INTERM_BENCH_RES) -> ret = -ENOSYS(-38)
> [42949413.120000] rt_tmbench_ioctl_rt -1070594560
> [42949414.070000] KERNEL: rt_tmbench_ioctl_nrt got request -1070594560
> [42949414.090000] rt_tmbench_ioctl_nrt: request
> -1070594560(RTTST_RTIOC_INTERM_BENCH_RES) -> ret = -ENOSYS(-38)
> [42949414.120000] rt_tmbench_ioctl_rt -1070594560
> [42949415.070000] KERNEL: rt_tmbench_ioctl_nrt got request -1070594560
> [42949415.090000] rt_tmbench_ioctl_nrt: request
> -1070594560(RTTST_RTIOC_INTERM_BENCH_RES) -> ret = -ENOSYS(-38)
> [42949415.120000] rt_tmbench_ioctl_rt -1070594560
> [42949415.290000] KERNEL: rt_tmbench_ioctl_nrt got request -1071118831
> [42949415.310000] rt_tmbench_ioctl_nrt: request -1071118831 -> ret =
> -ENOTTY(-25)
>
>
>
> The RTTST_RTIOC_INTERM_BENCH_RES request is received by
> rt_tmbench_ioctl_nrt and rt_tmbench_ioctl_rt. Is this normal on arm?
> (on my x86 this happens only at the beginning of a test-run)
Remove your instrumentation printfs from the user space part. They
always switch the task to secondary mode in order to dump the messages.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-10-18 12:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 15:39 [Xenomai-help] Adeos/Xenomai Arm Port 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 15:16 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.
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=45361F0C.1010007@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=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.