All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Shepherd <mcs@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Success! (was Re: Tests with 2.5rc1)
Date: Wed, 22 Apr 2009 18:43:20 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0904221805420.16285@domain.hid> (raw)
In-Reply-To: <49EF5149.9090609@domain.hid>


On Wed, 22 Apr 2009, Gilles Chanteperdrix wrote:
>...
> We must tell everyone on this list that high-res timers work for the
> current hardware we run our tests on, so that people do not conclude
> that hi-res timers do not work with Xenomai.
>
> So, I see from previous posts that you have PM-timers enabled, could you
> try to re-enable high_res_timers, and disable PM-timers ?

Yes, enabling HIGH_RES_TIMERS and disabling X86_PM_TIMER also fixes
the problem. In detail, after I re-enabled HIGH_RES_TIMERS, and
enabled EMBEDDED so that I could change the X86_PM_TIMER option, I
recompiled the kernel 4 times, toggling just the state of the
X86_PM_TIMER option. The results were as follows:

In the two cases where X86_PM_TIMER was enabled, the normal dd test
reliably hung the computer after about half a minute, leaving the
computer completely unresponsive to the keyboard and to pings from
other machines. Leading up to these hangs, top reported that dd was
getting very little CPU time, even though nothing else was running. I
limited dd to copying 5.1GB at a time, by setting its count argument
to 10000000, and was thus able to verify that dd eventually completed,
and that at that point, the system returned to normal, except that the
clock resumed from where it had been when the hang started, and was
thus left running slow. In other words, dd ran normally, but the clock
that would have otherwise allowed the scheduler to switch to other
tasks, stalled until dd finished.

In the two cases where X86_PM_TIMER was disabled, the system worked
fine. The dd process reliably got at least 95% of the CPU time when
nothing else was running, and never hung the computer.

Martin


  reply	other threads:[~2009-04-23  1:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 18:05 [Xenomai-help] Tests with 2.5rc1 Martin Shepherd
2009-04-20 18:28 ` Gilles Chanteperdrix
2009-04-20 19:16   ` Martin Shepherd
2009-04-20 22:13   ` [Xenomai-help] Success! (was Re: Tests with 2.5rc1) Martin Shepherd
2009-04-22 17:18     ` Gilles Chanteperdrix
2009-04-23  1:43       ` Martin Shepherd [this message]
2009-04-20 18:34 ` [Xenomai-help] Tests with 2.5rc1 Gilles Chanteperdrix
2009-04-20 18:46   ` Martin Shepherd

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=Pine.LNX.4.64.0904221805420.16285@domain.hid \
    --to=mcs@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.