From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Franz Engel <franz_lambert_engel@yahoo.de>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] High latency and smi with intel vendor chip
Date: Thu, 27 Jun 2013 20:35:42 +0200 [thread overview]
Message-ID: <51CC85FE.7080308@xenomai.org> (raw)
In-Reply-To: <51C45C6F.9080109@siemens.com>
On 06/21/2013 04:00 PM, Jan Kiszka wrote:
> On 2013-06-21 15:07, Franz Engel wrote:
>> Hi,
>>
>> In my dmesg I get the following message:
>> dmesg | grep -i xeno
>> [ 4.478964] I-pipe: head domain Xenomai registered.
>> [ 4.494089] Xenomai: hal/x86_64 started.
>> [ 4.505969] Xenomai: scheduling class idle registered.
>> [ 4.521300] Xenomai: scheduling class rt registered.
>> [ 4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The Beach) loaded.
>> [ 4.559065] Xenomai: debug mode enabled.
>> [ 4.579351] Xenomai: SMI-enabled chipset found
>> [ 4.592628] Xenomai: SMI workaround failed!
>> [ 4.605677] Xenomai: starting native API services.
>> [ 4.619979] Xenomai: starting POSIX services.
>> [ 4.633088] Xenomai: starting RTDM services.
>>
>>
>> And I have very high latencies. I read that I should try to insert my the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c file.
>
> That is no longer true since 2.6.2.1. Xenomai already detects your LPC
> (see above), but the BIOS has apparently locked SMI disabling down.
This change was made after 2.6.2.1. With 2.6.2.1, it is still necessary
to add the ISA bridge ids to the list.
You do not have to bother if you use the smictrl tool, though.
--
Gilles.
prev parent reply other threads:[~2013-06-27 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1371808801.4609.xenomai@xenomai.org>
2013-06-21 13:07 ` [Xenomai] High latency and smi with intel vendor chip Franz Engel
2013-06-21 14:00 ` Jan Kiszka
2013-06-22 11:57 ` Franz Engel
2013-06-24 6:40 ` Jan Kiszka
2013-06-24 7:20 ` Jan Kiszka
2013-06-27 17:26 ` Franz Engel
2013-06-27 18:51 ` Gilles Chanteperdrix
2013-06-27 18:35 ` 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=51CC85FE.7080308@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=franz_lambert_engel@yahoo.de \
--cc=jan.kiszka@siemens.com \
--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.