From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <48F76362.4010104@domain.hid> Date: Thu, 16 Oct 2008 17:53:06 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20081016145757.935266172@domain.hid> <48F76068.7050903@domain.hid> In-Reply-To: <48F76068.7050903@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [PATCH 0/2] Fix and improve task/thread inquire services List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org Gilles Chanteperdrix wrote: > Jan Kiszka wrote: >> This series fixes the issues around rt_task_inquire I posted yesterday. >> Additionally, it introduces an analogous services pthread_inquire_np for >> the POSIX skin. That allows, among other things, to implement test cases >> for the upcoming fast xnsynch/mutex patches. > > Ok. Since this applies only for debugging purpose, and displaying > whether a task is in primary mode may be use badly by users, maybe we > should make this service a shadow syscall, and not export any interface > to use it. This would further avoid duplication between the native and > posix skins. Debugging is not the holy, exclusive business of Xenomai hackers. The inquire services are useful in libraries as well, when you want to check if the caller complies to the call convention ("don't use in primary mode", "caller's priority must not exceed X" or whatever). That said, I'm open for unifying the code, maybe introducing some xnthread_inquire. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux