From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4E0A47B6.2000008@domain.hid> Date: Tue, 28 Jun 2011 23:29:26 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : nucleus: Allow drop_u_mode syscall from any context List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xenomai core On 06/28/2011 11:01 PM, GIT version control wrote: > Module: xenomai-jki > Branch: for-upstream > Commit: 5597470d84584846875e8a35309e6302c768addf > URL: http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=5597470d84584846875e8a35309e6302c768addf > > Author: Jan Kiszka > Date: Tue Jun 28 22:10:07 2011 +0200 > > nucleus: Allow drop_u_mode syscall from any context > > xnshadow_sys_drop_u_mode already checks if the caller is a shadow. It > does that without issuing a warning message if the check fails - in > contrast to do_hisyscall_event. As user space may call this cleanup > service even for non-shadow threads (e.g. after shadow creation failed), > we better silence this warning. > > Signed-off-by: Jan Kiszka Jan, I have a branch here, which allocates u_mode in the shared heap, so, this syscall is about to become unnecessary. See: http://git.xenomai.org/?p=xenomai-gch.git;a=shortlog;h=refs/heads/u_mode -- Gilles.