[Xenomai-help] Xenomai Tests (WHAT and HOW)

[Xenomai-help] Xenomai Tests (WHAT and HOW)

[Didenko Sergey]

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

Dear Xenomai Experts

We have ported Xenomai to the ARM Platform.
To make sure that we have ported Linux + Xenomai correctly, we are running
the tests from the testsuite the Xenomai has.
clocktest
cyclick
latency

Do you have any documentation or explanation of WHAT and HOW these tests are
actually testing?

Sergey

[-- Attachment #2: Type: text/html, Size: 356 bytes --]

Re: [Xenomai-help] Xenomai Tests (WHAT and HOW)

[Gilles Chanteperdrix]

Didenko Sergey wrote:
> Dear Xenomai Experts
> 
> We have ported Xenomai to the ARM Platform.

To be more accurate, Xenomai was ported to the ARM Platform long ago by
Stelian Pop, the thing that you could claim is that you ported Xenomai
to your platform, but as far as I understood, Philippe did that job.

> To make sure that we have ported Linux + Xenomai correctly, we are
> running the tests from the testsuite the Xenomai has.
> clocktest
> cyclick
> latency
> 
> Do you have any documentation or explanation of WHAT and HOW these tests
> are actually testing?

No.

clocktest tests how much the Xenomai clock is drifting from Linux clock.

cyclictest and latency are both measuring latencies. cyclictest and
latency with no argument are measuring the user-space scheduling
latency, latency -T 1 is measuring the kernel-space scheduling latency,
and latency -T 2 is measuring the (kernel-space) interrupt latency. In
order to get meaningful results with these tests, you should apply some
load to the system, and let the test run a few hours.

There is also the klatency test, which measures the kernel-space
latencies without any user-space thread running (it makes a difference
on ARM).

There is also the "switchtest" test, which indicates whether context
switches are running correctly.

-- 
                                          Gilles