All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>, xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Remove unused mode parameter from COBALT_SYSCALL
Date: Thu, 02 Jul 2015 17:39:49 +0200	[thread overview]
Message-ID: <55955B45.5000201@siemens.com> (raw)
In-Reply-To: <559557C2.3040004@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 <jan.kiszka@siemens.com>
>> 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


  reply	other threads:[~2015-07-02 15:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1ZAgI1-0000jO-Kb@sd-51317.xenomai.org>
2015-07-02 15:24 ` [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Remove unused mode parameter from COBALT_SYSCALL Philippe Gerum
2015-07-02 15:39   ` Jan Kiszka [this message]
2015-07-02 16:30     ` Philippe Gerum
2015-07-02 16:44       ` Jan Kiszka
2015-07-02 16:49         ` Gilles Chanteperdrix
2015-07-02 16:56           ` Philippe Gerum
2015-07-02 17:03             ` Gilles Chanteperdrix
2015-07-02 17:09               ` Philippe Gerum
2015-07-02 16:56           ` Gilles Chanteperdrix
2015-07-02 17:31             ` Jan Kiszka
2015-07-02 17:35               ` Gilles Chanteperdrix
2015-07-02 17:55                 ` Gilles Chanteperdrix
2015-07-02 17:57                   ` Jan Kiszka
2015-07-02 18:00                     ` Gilles Chanteperdrix
2015-07-02 18:42                     ` Gilles Chanteperdrix
2015-07-02 18:49                       ` Jan Kiszka
2015-07-02 18:55                         ` Gilles Chanteperdrix
2015-07-02 19:32                           ` Jan Kiszka
2015-07-02 20:26                             ` Jan Kiszka
2015-07-03 10:51                               ` Gilles Chanteperdrix
2015-07-03 12:31                                 ` Gilles Chanteperdrix
2015-07-03 12:38                                   ` Gilles Chanteperdrix
2015-07-16 12:35                                     ` Jan Kiszka
2015-07-16 18:42                                       ` Jan Kiszka
2015-07-16 22:34                                         ` Gilles Chanteperdrix
2015-07-17  6:06                                           ` Jan Kiszka
2015-07-17  7:23                                             ` Gilles Chanteperdrix
2015-07-16 12:34                                 ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55955B45.5000201@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.