All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : nucleus: Allow drop_u_mode syscall from	any context
Date: Tue, 28 Jun 2011 23:29:26 +0200	[thread overview]
Message-ID: <4E0A47B6.2000008@domain.hid> (raw)
In-Reply-To: <E1QbfP2-0008Go-2L@xenomai.org>

On 06/28/2011 11:01 PM, GIT version control wrote:
> Module: xenomai-jki
> Branch: for-upstream
> Commit: 5597470d84584846875e8a35309e6302c768addf
> URL:    http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=5597470d84584846875e8a35309e6302c768addf
> 
> Author: Jan Kiszka <jan.kiszka@domain.hid>
> Date:   Tue Jun 28 22:10:07 2011 +0200
> 
> nucleus: Allow drop_u_mode syscall from any context
> 
> xnshadow_sys_drop_u_mode already checks if the caller is a shadow. It
> does that without issuing a warning message if the check fails - in
> contrast to do_hisyscall_event. As user space may call this cleanup
> service even for non-shadow threads (e.g. after shadow creation failed),
> we better silence this warning.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>

Jan,

I have a branch here, which allocates u_mode in the shared heap, so,
this syscall is about to become unnecessary.

See:
http://git.xenomai.org/?p=xenomai-gch.git;a=shortlog;h=refs/heads/u_mode

-- 
                                                                Gilles.


       reply	other threads:[~2011-06-28 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1QbfP2-0008Go-2L@xenomai.org>
2011-06-28 21:29 ` Gilles Chanteperdrix [this message]
2011-06-29  7:06   ` [Xenomai-core] [Xenomai-git] Jan Kiszka : nucleus: Allow drop_u_mode syscall from any context Jan Kiszka
2011-06-29  7:25     ` Gilles Chanteperdrix
2011-06-29  7:31       ` 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=4E0A47B6.2000008@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Xenomai-core@domain.hid \
    /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.