From: Jan Kiszka <jan.kiszka@domain.hid>
To: Daniel Schnell <daniel.schnell@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [BUG] recursive fault on cyclictest termination -- scalable sched?
Date: Fri, 25 May 2007 17:32:21 +0200 [thread overview]
Message-ID: <46570185.3030406@domain.hid> (raw)
In-Reply-To: <DD39B5C3F4963040ADC9768BE7E430CB01F547BA@is-hdq-exchange.marel.net>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Daniel Schnell wrote:
> Well, that may be related to the bug I am seeing when I am ending cyclictest with Ctrl-C, Recursive kernel Ooops and this is on plain 2.3.1
>
2.3.1 is definitely affected by this bug as well, as it also gained the
prio-coupling rework. But you have to have SCALABLE_SCHED enabled.
I got it. It is - as usual - a trivial one-liner:
--- xenomai.orig/ksrc/nucleus/shadow.c
+++ xenomai/ksrc/nucleus/shadow.c
@@ -186,7 +186,7 @@ static inline void rpi_init(void)
static inline void rpi_init_gk(struct __gatekeeper *gk)
{
- sched_initpq(&gk->rpislot.threadq, xnqueue_down, XNCORE_NR_PRIO);
+ sched_initpq(&gk->rpislot.threadq, xnqueue_down, XNCORE_MAX_PRIO);
}
static inline void rpi_none(xnthread_t *thread)
Happy weekend, =8)
Jan
PS: The maximum priority level has initialised to a wrong value, causing
threads with prio 0 to be placed out of the queue array.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-05-25 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 13:35 [Xenomai-core] [BUG] recursive fault on cyclictest termination -- scalable sched? Jan Kiszka
2007-05-25 13:45 ` Gilles Chanteperdrix
2007-05-25 13:55 ` Jan Kiszka
2007-05-25 14:09 ` Jan Kiszka
2007-05-25 14:12 ` Philippe Gerum
2007-05-25 14:18 ` Gilles Chanteperdrix
[not found] ` <DD39B5C3F4963040ADC9768BE7E430CB01F547BA@is-hdq-exchange.marel.net>
2007-05-25 14:34 ` Jan Kiszka
2007-05-25 15:32 ` Jan Kiszka [this message]
2007-05-27 1:51 ` Philippe Gerum
2007-05-25 13:50 ` 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=46570185.3030406@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=daniel.schnell@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.