From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <55955B45.5000201@siemens.com> Date: Thu, 02 Jul 2015 17:39:49 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <559557C2.3040004@xenomai.org> In-Reply-To: <559557C2.3040004@xenomai.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Remove unused mode parameter from COBALT_SYSCALL List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum , xenomai@xenomai.org On 2015-07-02 17:24, Philippe Gerum wrote: > On 07/02/2015 05:20 PM, git repository hosting wrote: >> Module: xenomai-jki >> Branch: for-forge >> Commit: 99736c29a21a5e5536f8db9e580fd11cdb0eb0f2 >> URL: http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=99736c29a21a5e5536f8db9e580fd11cdb0eb0f2 >> >> Author: Jan Kiszka >> Date: Thu Jul 2 17:12:39 2015 +0200 >> >> cobalt/kernel: Remove unused mode parameter from COBALT_SYSCALL > > We want to keep this. At some point, maybe, we will be able to use this > information to instrument the code with calling context guards, or as > the source of the mode data in the syscall table. Today, it's at least > useful inline documentation, without having to browse the table. This only makes sense when cobalt_sysmodes can be generated from it. Currently it isn't, and I bet there are already plenty of inconsistencies, minimizing the value captured via COBALT_SYSCALL massively. So we should either get rid of cobalt_sysmodes or of that parameter. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux