From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "Xenomai@xenomai.org" <Xenomai@xenomai.org>
Subject: Re: [Xenomai] [QUESTION] thread creation and hook function
Date: Mon, 15 Apr 2013 21:45:07 +0200 [thread overview]
Message-ID: <516C58C3.1080404@xenomai.org> (raw)
In-Reply-To: <516C0E3B.5050606@xenomai.org>
On 04/15/2013 04:27 PM, Philippe Gerum wrote:
> On 04/15/2013 04:18 PM, alex alex wrote:
>> pthread_set_name_np is called after the task creation and it seems that
>> the *_np function force to switch in secondary too...
>
> No, it does not. Maybe you should double-check the way you determine
> mode switches.
Yes, using SIGDEBUG is the recommended way to understand mode switches.
Anyway, a reason for parasite mode switches could be that Alexandre is
using the 3.2.21 kernel, which we know has issues with mprotect, maybe
he gets additional page faults?
--
Gilles.
next prev parent reply other threads:[~2013-04-15 19:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 16:58 [Xenomai] [QUESTION] thread creation and hook function alex alex
2013-04-13 17:41 ` Gilles Chanteperdrix
2013-04-13 18:20 ` alex alex
2013-04-13 20:55 ` Gilles Chanteperdrix
2013-04-13 22:41 ` alex alex
2013-04-13 23:05 ` Gilles Chanteperdrix
2013-04-13 23:07 ` Gilles Chanteperdrix
2013-04-13 23:37 ` Gilles Chanteperdrix
2013-04-15 8:47 ` alex alex
2013-04-15 9:14 ` Philippe Gerum
2013-04-15 10:25 ` alex alex
2013-04-15 12:36 ` Philippe Gerum
2013-04-15 13:05 ` Philippe Gerum
2013-04-15 13:08 ` Philippe Gerum
2013-04-15 13:43 ` alex alex
2013-04-15 13:48 ` alex alex
2013-04-15 14:06 ` Philippe Gerum
[not found] ` <CAPpP=rMsqp5SOfq8_dNUOZ5UFugNa-YwsLyT5WT4d01_UTWRMA@mail.gmail.com>
2013-04-15 14:27 ` Philippe Gerum
2013-04-15 19:45 ` Gilles Chanteperdrix [this message]
2013-04-16 7:03 ` Philippe Gerum
2013-04-15 19:43 ` 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=516C58C3.1080404@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai@xenomai.org \
--cc=rpm@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.