From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Stoidner, Christoph" <c.stoidner@arvero.de>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Sleeping function called from invalid context
Date: Tue, 9 Dec 2014 21:08:20 +0100 [thread overview]
Message-ID: <20141209200820.GM30777@hermes.click-hack.org> (raw)
In-Reply-To: <acbe2f0f37f447bea2205fcafd963830@EX132MBOX1A.de2.local>
On Tue, Dec 09, 2014 at 08:06:03PM +0000, Stoidner, Christoph wrote:
>
> Hi Gilles,
>
> >> Well, then you need to replace #ifdef CONFIG_PREEMPT_RT with
> >> CONFIG_PREEMPT_RT_FULL, and test the kernel version in wrappers.h to
> >> define CONFIG_PREEMPT_RT_FULL if CONFIG_PREEMPT_RT is dedined for
> >> old kernels.
>
> >I have applied both changes and try if this solves the my problem. If it works I will publish the patch here.
>
> below you can find the patch. It solves the problem concerning "sleeping function called from invalid context" when using PREEMPT RT. Would it be reasonable to apply that change to GIT repository?
Yes, of course.
> #ifndef DEFINE_SEMAPHORE
> /* Legacy DECLARE_MUTEX vanished in 2.6.37 */
> #define DEFINE_BINARY_SEMAPHORE(sem) DECLARE_MUTEX(sem)
> -#elif defined(CONFIG_PREEMPT_RT)
> -#define DEFINE_BINARY_SEMAPHORE(sem) DEFINE_SEMAPHORE(sem, 1)
> +#elif defined(CONFIG_PREEMPT_RT_FULL)
> +#define DEFINE_BINARY_SEMAPHORE(sem) DEFINE_SEMAPHORE(sem)
> #else
> #define DEFINE_BINARY_SEMAPHORE(sem) DEFINE_SEMAPHORE(sem)
> #endif
Why that change? I mean in 2.6.37, the define was CONFIG_PREEMPT_RT
anwyay.
--
Gilles.
next prev parent reply other threads:[~2014-12-09 20:08 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 14:19 [Xenomai] Sleeping function called from invalid context Stoidner, Christoph
2014-12-06 14:25 ` Gilles Chanteperdrix
2014-12-06 15:11 ` Stoidner, Christoph
2014-12-07 12:32 ` Stoidner, Christoph
2014-12-07 12:40 ` Gilles Chanteperdrix
2014-12-07 13:50 ` Stoidner, Christoph
2014-12-07 13:52 ` Gilles Chanteperdrix
2014-12-07 15:05 ` Stoidner, Christoph
2014-12-09 20:06 ` Stoidner, Christoph
2014-12-09 20:08 ` Gilles Chanteperdrix [this message]
2014-12-09 20:18 ` Stoidner, Christoph
2014-12-09 20:24 ` Gilles Chanteperdrix
2014-12-09 20:34 ` Stoidner, Christoph
2014-12-09 20:37 ` Gilles Chanteperdrix
2014-12-09 20:47 ` Stoidner, Christoph
2014-12-09 20:55 ` Gilles Chanteperdrix
2014-12-09 20:49 ` Stoidner, Christoph
2014-12-09 20:59 ` Gilles Chanteperdrix
2014-12-10 16:23 ` Stoidner, Christoph
2014-12-10 16:26 ` Gilles Chanteperdrix
2014-12-10 18:23 ` Stoidner, Christoph
2014-12-10 18:41 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2014-12-10 18:58 Stoidner, Christoph
2014-12-10 19:01 ` Gilles Chanteperdrix
2014-12-11 10:00 ` Stoidner, Christoph
2014-12-11 10:05 ` Gilles Chanteperdrix
2014-12-11 10:18 ` Stoidner, Christoph
2014-12-11 10:22 ` Gilles Chanteperdrix
2014-12-11 10:29 ` Stoidner, Christoph
2014-12-11 10:47 ` Gilles Chanteperdrix
2014-12-11 11:17 ` Stoidner, Christoph
2014-12-11 14:47 ` Gilles Chanteperdrix
2014-12-11 15:47 ` Stoidner, Christoph
2014-12-11 16:06 ` Gilles Chanteperdrix
2014-12-11 16:31 ` Stoidner, Christoph
2014-12-11 16:38 ` Gilles Chanteperdrix
2014-12-11 19:23 ` Stoidner, Christoph
2014-12-12 16:42 ` Stoidner, Christoph
2014-12-15 11:42 ` Stoidner, Christoph
2014-12-15 13:23 ` Gilles Chanteperdrix
2014-12-15 13:29 ` Stoidner, Christoph
2014-12-15 14:20 ` Gilles Chanteperdrix
2014-12-15 15:11 ` Stoidner, Christoph
2014-12-15 15:19 ` Gilles Chanteperdrix
2014-12-17 12:24 ` Stoidner, Christoph
2014-12-17 12:38 ` Gilles Chanteperdrix
2014-12-17 13:22 ` Gilles Chanteperdrix
2014-12-17 15:46 ` Gilles Chanteperdrix
2014-12-17 22:40 ` Stoidner, Christoph
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=20141209200820.GM30777@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=c.stoidner@arvero.de \
--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.