From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4D5137B0.8050006@domain.hid> Date: Tue, 08 Feb 2011 13:31:44 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4D5039AD.2070205@domain.hid> <4D50433D.1040804@domain.hid> <1297154320.2023.6.camel@domain.hid> <1297156556.2023.9.camel@domain.hid> <4D513278.4090606@domain.hid> <1297167172.2023.11.camel@domain.hid> <4D513427.6050707@domain.hid> <1297167750.2023.13.camel@domain.hid> In-Reply-To: <1297167750.2023.13.camel@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Exception handlers in primary domain / user-space signals List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: xenomai@xenomai.org Philippe Gerum wrote: > On Tue, 2011-02-08 at 13:16 +0100, Gilles Chanteperdrix wrote: >> I was not talking about the Xenomai case specifically, but since Henri >> would like to have the full signals implementation with Xenomai, this >> does a apply to Xenomai too. >> >> > > I think we all agree that having a complete signal implementation for > Xenomai in pure rt mode won't happen overnight. So the point is now: how > could it be mimicked, at least for the most useful part. > My point is that whatever you do, a switch user-kernel, then kernel-user is not going to be lightweight, so avoiding it in the application in the first place may be a better idea. My aim with implementing complete signals was rather for things like timer_* and mq_notify, where the interface requires them, I did not even imagine implementing SIGFPE, SIGILL, SIGTRAP, which I thought could not be time critical anyway, for the reasons explained earlier. So, my question (rather to Henri) is: what would we need SIGFPE, SIGILL, SIGTRAP in an real-time application for? -- Gilles.