From: Philippe Gerum <rpm@xenomai.org>
To: Jim Cromie <jim.cromie@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] some results on my laptop
Date: Thu, 02 Feb 2006 23:59:52 +0100 [thread overview]
Message-ID: <43E28EE8.3020103@domain.hid> (raw)
In-Reply-To: <43E288AA.3050203@domain.hid>
Hi Jim,
Jim Cromie wrote:
>
> some random sucesses ..
>
> Ive been running an ipipe kernel as the default since shortly after 1/7.
> Since then, Ive had a couple of freezes on boot,
> and sometimes bash's auto-complete takes longer to complete,
Eh? Maybe the CONFIG_PCI_MSI syndrom again?
> but other than that, things have been solid.
>
> But that kernel wasnt configured using scripts/prepare-kernel.sh,
> so was missing the xeno_* modules.
>
<snip>
> RTS| -4814| -4583| -2582| 0| 00:02:00/00:02:00
>
>
> This was run on a pentium-M laptop,
> with cpu-clock running at 600 MHz, (capable of 1.7 GHz)
> I presume this might explain the negative latancies.
> Im aware this is un-supported ..
>
The negative values are just there because even at 600Mhz, the timing anticipation
applied by the nucleus to compensate for the intrinsic latency of the box is too
high; i.e. the nucleus performs a bit too well latency-wise, so the anticipated
timer ticks end up being a bit early on schedule. IOW, all is fine. Given the
figures above, you could probably reduce the anticipation factor by setting the
CONFIG_XENO_HW_SCHED_LATENCY (Machine menu) parameter to, say, 2500 nanoseconds
(the default null value tells the nucleus to use the pre-calibrated value, which
might be higher than this for your setup).
Btw, I'm not sure if you enabled the local APIC in your kernel config; if you did
not, you should: there is no reason to keep using the braindamage 8254 PIT when a
LAPIC is available with your CPU.
> The only thing that looks wrong is the test-duration.
> I asked for 120 sec, it gave me 40 samples.
> The test did take 120 to run.
>
You should disable the ACPI support if enabled, and especially everything related
to the CPUfreq scaling and power suspend.
--
Philippe.
next prev parent reply other threads:[~2006-02-02 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 22:33 [Xenomai-core] some results on my laptop Jim Cromie
2006-02-02 22:59 ` Philippe Gerum [this message]
2006-02-03 0:26 ` Jim Cromie
2006-02-03 7:51 ` Philippe Gerum
2006-02-03 8:17 ` Jan Kiszka
2006-02-03 8:26 ` Jan Kiszka
2006-02-03 8:58 ` Philippe Gerum
2006-02-03 9:18 ` Anders Blomdell
2006-02-03 9:26 ` Jan Kiszka
2006-02-03 9:14 ` Anders Blomdell
2006-02-03 9:35 ` Jan Kiszka
2006-02-03 10:01 ` Anders Blomdell
2006-02-03 10:20 ` Jan Kiszka
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=43E28EE8.3020103@domain.hid \
--to=rpm@xenomai.org \
--cc=jim.cromie@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.