All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Didenko Sergey <didenkos@domain.hid>
Cc: xenomai@xenomai.org, mohamad.sharifi@domain.hid
Subject: Re: [Xenomai-help] Xenomai Tests (WHAT and HOW)
Date: Mon, 19 Oct 2009 14:24:23 +0200	[thread overview]
Message-ID: <4ADC5A77.1060708@domain.hid> (raw)
In-Reply-To: <1f3e02580910190417p67796a2k8d9db0253bd59033@domain.hid>

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



      reply	other threads:[~2009-10-19 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 11:17 [Xenomai-help] Xenomai Tests (WHAT and HOW) Didenko Sergey
2009-10-19 12:24 ` Gilles Chanteperdrix [this message]

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=4ADC5A77.1060708@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=didenkos@domain.hid \
    --cc=mohamad.sharifi@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.