From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Troubles with switchtest
Date: Wed, 13 May 2009 22:59:43 +0200 [thread overview]
Message-ID: <4A0B34BF.3020707@domain.hid> (raw)
In-Reply-To: <4A0AE9EF.1010107@domain.hid>
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Jan Kiszka wrote:
>>>>> Hi Gilles,
>>>>>
>>>>> I'm currently facing a nasty effect with switchtest over latest git head
>>>>> (only tested this so far): running it inside my test VM (ie. with
>>>>> frequent excessive latencies) I get a stalled Linux timer IRQ quite
>>>>> quickly. System is otherwise still responsive, Xenomai timers are still
>>>>> being delivered, other Linux IRQs too. switchtest complained about
>>>>>
>>>>> "Warning: Linux is compiled to use FPU in kernel-space."
>>>>>
>>>>> when it was started. Kernels are 2.6.28.9/ipipe-x86-2.2-07 and
>>>>> 2.6.29.3/ipipe-x86-2.3-01 (LTTng patched in, but unused), both show the
>>>>> same effect.
>>>>>
>>>>> Seen this before?
>>>> The warning about Linux being compiled to use FPU in kernel-space means
>>>> that you enabled soft RAID or compiled for K7, Geode, or any other
>>> RAID is on (ordinary server config).
>> By the way, I wonder how MMX accelerated software raid works on K7,
>> since the way I understand the code, calls to kernel_fpu_begin() can not
>> be nested.
>>
>> If you think they can be nested, then we can make switchtest test fpu in
>> Linux kernel-space when these options are enabled.
>
> Sorry, I haven't looked that close into the in-kernel FPU handling so
> far. What users are nested in the standard kernel? Or is it RAID in itself?
RAID uses FPU. And on K7, basic things like clearing or copying user
pages, or even large memcpy do use FPU too. So, I would expect that when
enabling both, they could happen to be nested.
--
Gilles.
next prev parent reply other threads:[~2009-05-13 20:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 12:49 [Xenomai-core] Troubles with switchtest Jan Kiszka
2009-05-13 12:58 ` Gilles Chanteperdrix
2009-05-13 13:18 ` Jan Kiszka
2009-05-13 13:22 ` Philippe Gerum
2009-05-13 15:28 ` [Xenomai-core] [PATCH] Fix host IRQ propagation (was: Troubles with switchtest) Jan Kiszka
2009-05-13 15:55 ` Philippe Gerum
2009-05-13 16:10 ` [Xenomai-core] [PATCH] Fix host IRQ propagation Jan Kiszka
2009-05-13 20:50 ` Philippe Gerum
2009-05-14 10:20 ` Jan Kiszka
2009-05-14 10:49 ` Philippe Gerum
2009-05-14 11:00 ` Jan Kiszka
2009-05-14 11:10 ` Philippe Gerum
2009-05-14 12:52 ` Gilles Chanteperdrix
2009-05-14 13:00 ` Philippe Gerum
2009-05-14 13:10 ` Gilles Chanteperdrix
2009-05-17 10:32 ` Philippe Gerum
2009-05-13 18:14 ` Gilles Chanteperdrix
2009-05-13 18:24 ` Jan Kiszka
2009-05-13 19:06 ` [Xenomai-core] [PATCH] Fix host IRQ propagation (was: Troubles with switchtest) Martin Shepherd
2009-05-14 10:34 ` [Xenomai-core] [PATCH] Fix host IRQ propagation Jan Kiszka
2009-05-14 11:56 ` Gilles Chanteperdrix
2009-05-14 12:02 ` Jan Kiszka
2009-05-13 15:09 ` [Xenomai-core] Troubles with switchtest Gilles Chanteperdrix
2009-05-13 15:40 ` Jan Kiszka
2009-05-13 20:59 ` Gilles Chanteperdrix [this message]
2009-05-14 8:18 ` Jan Kiszka
2009-05-14 8:35 ` Gilles Chanteperdrix
2009-05-14 8:38 ` Jan Kiszka
2009-05-14 8:42 ` Gilles Chanteperdrix
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=4A0B34BF.3020707@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@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.