From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] CONFIG_PREEMPT doesn't work with ADEOS
Date: Tue, 18 Apr 2006 14:16:54 +0200 [thread overview]
Message-ID: <4444D8B6.3020004@domain.hid> (raw)
In-Reply-To: <4444D5F6.2010006@domain.hid>
Jan Kiszka wrote:
> Philippe Gerum wrote:
>
>>Philippe Gerum wrote:
>>
>>>Bernhard Walle wrote:
>>>
>>>
>>>>Hello,
>>>>
>>>>I have a kernel 2.6.15.6 with
>>>>http://download.gna.org/adeos/patches/v2.6/i386/adeos-ipipe-2.6.15-i386-1.2-03.patch
>>>>
>>>>patch. In this configuration, CONFIG_PREEMPT doesn't work any more,
>>>>i.e. the kernel is not preempted.
>>>>
>>>
>>>How do you check this?
>>>
>>
>>Forget about this question. I'm going to give a look at your testcase
>>when time allows. Thanks.
>>
>
>
> I did, and I can confirm this (2.6.16, original ipipe-1.2-03 applied,
> ipipe on vs. off). Maybe something related to the TASK_ATOMICSWITCH changes?
>
Don't know yet, I'm rebuilding an instrumented kernel, but considering
that we don't even have local echo of keystrokes, I'd rather think of
IRQs lagging in the pipeline log. More news later.
>
>>>>With the kernel without ADEOS patch, it works fine. A test program is
>>>>at http://www.bwalle.de/temp/kern-preempt.tar.bz2.
>>>>
>>>>Do you know what's wrong?
>>>>
>>>>
>>>>Regards,
>>>> Bernhard
>>>
>>>
>>>
>
> Jan
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main
--
Philippe.
next prev parent reply other threads:[~2006-04-18 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 11:14 [Adeos-main] CONFIG_PREEMPT doesn't work with ADEOS Bernhard Walle
2006-04-18 11:44 ` Philippe Gerum
2006-04-18 11:50 ` Philippe Gerum
2006-04-18 12:05 ` Jan Kiszka
2006-04-18 12:16 ` Philippe Gerum [this message]
2006-04-18 12:54 ` Philippe Gerum
2006-04-18 13:01 ` Philippe Gerum
2006-04-18 14:00 ` Philippe Gerum
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=4444D8B6.3020004@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=jan.kiszka@domain.hid \
/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.