From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <48F7BA7F.3030007@domain.hid> Date: Fri, 17 Oct 2008 00:04:47 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <48F6195C.7070801@domain.hid> <48F6492C.4090500@domain.hid> <48F660E7.8090906@domain.hid> <48F79AF9.6030303@domain.hid> <48F7B5F8.7020105@domain.hid> In-Reply-To: <48F7B5F8.7020105@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] rt_task_info.status encoding List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai-core Jan Kiszka wrote: > I start to believe we are arguing with different (miss-)use case in > mind. Mine is definitely not about "helping" the user to switch the > thread mode even more actively. It is about validating application > states, it is about thread state reflection without any other actions > than reporting errors. T_PRIMARY is part of the picture for the dual > kernel Xenomai version, and it will remain such as long as there are two > kernels. Even better, it is a very helpful application debugging tool > when it comes to runtime validation of their real-time behavior. Again, > it is NOT about promoting more use of rt_task_set_mode! SIGXCPU may be used validate current thread mode, and it has the advantage that it can not be misused. -- Gilles.