Re: [Xenomai-help] Adeos/Xenomai Arm Port

[Jan Kiszka <jan.kiszka@domain.hid>]

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

Schlägl Manfred jun. wrote:
>>> Again Latency:
>>>
>>> -sh-3.00#  time ./run -- -t 1 -p 1000 -T 10 
>>> *
>>> *
>>> * Type ^C to stop this application.
>>> *
>>> *
>>> Using /lib/modules/2.6.15.7/kernel/kernel/xenomai/nucleus/xeno_nucleus.ko
>>> Using /lib/modules/2.6.15.7/kernel/kernel/xenomai/skins/native/xeno_native.ko
>>> Using /lib/modules/2.6.15.7/kernel/kernel/xenomai/skins/rtdm/xeno_rtdm.ko
>>> Using /lib/modules/2.6.15.7/kernel/drivers/xenomai/testing/xeno_timerbench.ko
>>> == Sampling period: 1000 us
>>> == Test mode: in-kernel periodic task
>>> == All results in microseconds
>>> warming up...
>>> RTT|  00:00:01  (in-kernel periodic task, 1000 us period, priority 99)
>>> RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat
>>> worst
>>> RTD|      11.680|      16.586|      36.126|       0|      11.680|
>>> 36.126
>>> RTD|      11.182|      17.092|      43.947|       0|      11.182|
>>> 43.947
>>> RTD|      11.521|      17.091|      65.411|       0|      11.182|
>>> 65.411
>>> RTD|      11.981|      17.116|      63.388|       0|      11.182|
>>> 65.411
>>> RTD|      11.919|      17.121|      66.767|       0|      11.182|
>>> 66.767
>>> RTD|      12.354|      17.178|      42.996|       0|      11.182|
>>> 66.767
>>> RTD|      11.884|      17.122|      66.315|       0|      11.182|
>>> 66.767
>>> RTD|      11.849|      17.132|      65.287|       0|      11.182|
>>> 66.767
>>> RTD|      11.578|      17.093|      66.824|       0|      11.182|
>>> 66.824
>>> ---|------------|------------|------------|--------|-------------------------
>>> RTS|-1095668.296|       0.001|      93.252|   93340|
>>> 00:00:10/00:00:10
>> Looks like you forgot to recompile the user space part after applying my
>> patch. It changes the ABI between the driver and the test tool, so both
>> sides have to be in sync.
>>
> 
> User and Kernel-space are in sync, but i'm using xenomai-2.2.3:
> 
> typedef struct rttst_tmbench_config {
>     int                     mode;
> -   uint64_t                period;
>     int                     priority;    
> +   uint64_t                period;
>     int                     warmup_loops;
>     int                     histogram_size;
>     int                     histogram_bucketsize;
>     int                     freeze_max;
> } rttst_tmbench_config_t;
> 
> RTTST_RTIOC_TMBENCH_START works
> 
> but every RTTST_RTIOC_INTERM_BENCH_RES is received by
> rt_tmbench_ioctl_nrt (can't handle this request -> -ENOSYS) and
> rt_tmbench_ioctl_rt. is this normal?

Yes, it is. After each of these real-time-requiring services comes a
printf in the display task of latency. So the task is switch to
secondary mode again and the next RTTST_RTIOC_INTERM_BENCH_RES has to
switch it back.

Maybe the broken output of the latency test summary correlates to the
timer issue, maybe there is just a problem in the data transfer from the
driver to the user space application.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]