From: Philippe Gerum <rpm@xenomai.org>
To: xenomai@xenomai.org, xenomai-git@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/posix/syscall: Exclude sc_cobalt_get_current from debug warnings
Date: Fri, 20 Feb 2015 17:49:40 +0100 [thread overview]
Message-ID: <54E765A4.20909@xenomai.org> (raw)
In-Reply-To: <E1YOpt4-0000oo-4D@sd-51317.xenomai.org>
On 02/20/2015 04:53 PM, git repository hosting wrote:
> Module: xenomai-jki
> Branch: for-forge
> Commit: fc2d70475f4f86da30e68a569e7641982f4dd8e1
> URL: http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=fc2d70475f4f86da30e68a569e7641982f4dd8e1
>
> Author: Jan Kiszka <jan.kiszka@siemens.com>
> Date: Fri Feb 20 16:50:15 2015 +0100
>
> cobalt/posix/syscall: Exclude sc_cobalt_get_current from debug warnings
>
> This syscall is used for probing the context, thus may be triggered by
> non-RT threads as well which we should not report as potential error.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
This would mean that sc_cobalt_get_current is considered valid from any
process, including those which did not issue sc_cobalt_bind in the first
place.
Do we depend on this today, or are we granting an extended access with
this patch?
--
Philippe.
next parent reply other threads:[~2015-02-20 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YOpt4-0000oo-4D@sd-51317.xenomai.org>
2015-02-20 16:49 ` Philippe Gerum [this message]
2015-02-20 17:09 ` [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/posix/syscall: Exclude sc_cobalt_get_current from debug warnings Jan Kiszka
2015-02-20 19:56 ` Philippe Gerum
2015-03-10 15:27 ` Jan Kiszka
2015-03-15 16:17 ` Philippe Gerum
2015-03-10 14:46 ` 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=54E765A4.20909@xenomai.org \
--to=rpm@xenomai.org \
--cc=xenomai-git@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.