From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] Fix host IRQ propagation
Date: Thu, 14 May 2009 14:02:14 +0200 [thread overview]
Message-ID: <4A0C0846.50502@domain.hid> (raw)
In-Reply-To: <4A0C06DD.90104@domain.hid>
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Martin Shepherd wrote:
>>> On Wed, 13 May 2009, Jan Kiszka wrote:
>>>> ...
>>>> Martin, could you check if this helps you, too?
>>> It doesn't appear to help. To check, first I turned on the HPET and PM
>>> timer options, and recompiled the kernel without your patch, to verify
>>> that this reproduced the problem. I then manually applied your patch
>>> to include/asm-generic/xenomai/hal.h in the kernel source tree,
>>> recompiled the kernel, installed etc, and rebooted. However even with
>>> the patch in place, whenever I ran:
>>>
>>> dd if=/dev/zero of=/dev/null count=20000000
>>>
>>> then initially top showed that dd was getting very little CPU time
>>> (<10%), then after 30 seconds or so, the system became completely
>>> unresponsive until the dd ended. This is how it acts without the patch
>>> as well. So it doesn't appear that the patch has made any difference
>>> to this problem.
>> Hmm, so there is no Xenomai task running during this test, just Linux
>> load? Tried to reproduce with my kernel here (both HPET and PM enabled,
>> as usual), but no success. Strange.
>
> Just having HPET and PM_TIMER enabled is not enough: your CPU needs to
> actually have an HPET timer or PM timer.
That's the case for practically any modern system. So I bet the "trick"
is to make Linux _use_ one of them - in favor of the normally better
suited LAPIC. Need to check again what the reasons for this switch could
be. One that comes to my mind is problems of LAPIC vs. power management.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-05-14 12:02 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 [this message]
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
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=4A0C0846.50502@domain.hid \
--to=jan.kiszka@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.