From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <516C58C3.1080404@xenomai.org> Date: Mon, 15 Apr 2013 21:45:07 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <516998B7.9090901@xenomai.org> <5169C63B.1070406@xenomai.org> <5169EC2C.4000101@xenomai.org> <516BC4DF.3030302@xenomai.org> <516BF43D.7070708@xenomai.org> <516C094F.2050107@xenomai.org> <516C0E3B.5050606@xenomai.org> In-Reply-To: <516C0E3B.5050606@xenomai.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] [QUESTION] thread creation and hook function List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: "Xenomai@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.