From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Tschaeche IT-Services <services@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Force switch back to primary domain
Date: Thu, 04 Feb 2010 15:30:25 +0100 [thread overview]
Message-ID: <4B6ADA01.2080803@domain.hid> (raw)
In-Reply-To: <20100204105700.GB20669@domain.hid>
Tschaeche IT-Services wrote:
> Hi all,
>
> my scenario is as follows:
>
> - Xenomai 2.4.10, Linux 2.6.30.10
It would be nice if you could try Xenomai 2.5.1, the latest stable
release, to see if you are not having a problem that we already fixed.
> - rtdm-driver, defining ioctl_rt and ioctl_nrt
> - user space task migrated with rt_task_shadow()
> to primary domain
> - user space task is in a loop calling rt_dev_ioctl()
>
> what happens:
>
> as long as user space task does not switch to secondary domain
> user space task comes into ioctl_rt of my driver, which
> waits on an event with rtdm_event_wait() - fine :-)
>
>
> but, when user space task gets a Linux signal (SIGTRAP
> caused by breakpoint), user space task switches
> to secondary domain executing the signal handler,
> which returns after handling the signal - fine up to here.
>
> then, i would like to switch back to primary domain using:
>
> rt_task_set_mode(0, T_PRIMARY, NULL);
You do not need to do that.
>
> which returns without error. but, when calling rt_dev_ioctl()
> again, the non realtime version function of the driver ioctl_nrt
> is called (where i can't use rtdm_event_wait()).
in ioctl_nrt, return -ENOSYS, Xenomai will switch back your task to
primary mode, and call the rt ioctl.
--
Gilles Chanteperdrix, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-02-04 14:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 10:57 [Xenomai-help] Force switch back to primary domain Tschaeche IT-Services
2010-02-04 14:30 ` Gilles Chanteperdrix [this message]
2010-02-05 10:37 ` Tschaeche IT-Services
2010-02-05 11:19 ` Gilles Chanteperdrix
2010-02-05 11:50 ` Tschaeche IT-Services
2010-02-05 12:39 ` Henri Roosen
2010-02-05 13:34 ` Gilles Chanteperdrix
2010-02-05 14:38 ` Jan Kiszka
2010-02-05 15:27 ` Henri Roosen
2010-02-08 14:03 ` Gilles Chanteperdrix
2010-02-08 14:33 ` Henri Roosen
2010-02-09 10:06 ` Gilles Chanteperdrix
2010-02-09 10:09 ` Jan Kiszka
2010-02-09 10:14 ` Henri Roosen
2010-02-12 15:57 ` Henri Roosen
2010-02-12 16:02 ` Gilles Chanteperdrix
2010-02-12 17:16 ` Gilles Chanteperdrix
2010-02-12 17:20 ` Gilles Chanteperdrix
2010-02-15 9:07 ` Henri Roosen
2010-02-15 9:35 ` Jan Kiszka
2010-02-15 9:36 ` Philippe Gerum
2010-02-15 10:33 ` Henri Roosen
2010-02-15 10:47 ` 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=4B6ADA01.2080803@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=services@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.