From: Jan Kiszka <jan.kiszka@domain.hid>
To: Kim Chuan Lim <lim.kim.chuan@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RT timer help
Date: Fri, 14 Jul 2006 10:51:40 +0200 [thread overview]
Message-ID: <44B75B1C.7070400@domain.hid> (raw)
In-Reply-To: <e325d110607140124s58999affoe349860eeede0de4@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
Kim Chuan Lim wrote:
> dmesg..
>
> I-pipe: Domain Xenomai registered.
> Xenomai: hal/x86 started.
> Xenomai: real-time nucleus v2.2-rc3 (Engines Of Creation) loaded.
> Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> CONFIG_XENO_HW_SMI_WORKAROUND). You may encounter high
> interrupt latencies!
Check the related configuration under Real-time sub-system -> Machine ->
SMI workaround. Switching it on is recommended (but shouldn't be the
reason for the strange timing - but who knows...).
> Xenomai: starting native API services.
> Xenomai: starting POSIX services.
> Xenomai: starting RTDM services.
>
> Pentium 4 3.2GHz with HT.
> My current configuration only able to detect one CPU. :(
Again, HT is EVIL for real-time because it's only pseudo SMP. You cannot
reliably predict when central CPU resources are blocked by any of the
virtual CPUs. Thus, you may suffer from ugly priority inversions between
Linux running on one HT sub-core and Xenomai running on the other, but
both competing for shared resources.
> cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 15
> model : 2
> model name : Intel(R) Pentium(R) 4 CPU 3.20GHz
> stepping : 9
> cpu MHz : 3216.093
> cache size : 512 KB
> physical id : 0
> siblings : 1
> core id : 0
> cpu cores : 1
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up
> cid xtpr
> bogomips : 6440.74
>
>
> zcat /proc/config.gz
> I have disabled Power Management.
>
> #
> # Power management options (ACPI, APM)
> #
> # CONFIG_PM is not set
>
> #
> # ACPI (Advanced Configuration and Power Interface) Support
> #
> # CONFIG_ACPI is not set
>
> #
> # CPU Frequency scaling
> #
> # CONFIG_CPU_FREQ is not set
>
> Please find the attachment for my /proc/config.gz
>
Some suggestions for tests:
o switch on SMI workaround
o switch off SMP, if that helps, re-enable but leave SCHED_SMT
(hyperthreading) disabled
o switch on ACPI, but leave ACPI_PROCESSOR off
Jan
PS: CONFIG_XENO_OPT_TIMING_PERIODIC is not required unless you really
base your timing on a periodically ticking timer instead of the default
one-shot high-resolution mode. Otherwise this switch only adds overhead.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-07-14 8:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 12:03 [Xenomai-help] RT timer help Kim Chuan Lim
2006-07-13 12:14 ` Gilles Chanteperdrix
2006-07-13 14:37 ` Kim Chuan Lim
2006-07-13 14:47 ` Gilles Chanteperdrix
2006-07-13 16:02 ` Kim Chuan Lim
2006-07-13 16:05 ` Gilles Chanteperdrix
2006-07-13 16:46 ` Kim Chuan Lim
2006-07-13 16:51 ` Gilles Chanteperdrix
[not found] ` <e325d110607131026qdb0aac8p53bb9f1ddad58181@domain.hid>
2006-07-13 19:24 ` Gilles Chanteperdrix
2006-07-14 8:24 ` Kim Chuan Lim
2006-07-14 8:51 ` Jan Kiszka [this message]
2006-07-14 10:13 ` Kim Chuan Lim
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=44B75B1C.7070400@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=lim.kim.chuan@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.