All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Dmitry Adamushko <dmitry.adamushko@domain.hid>
Cc: xenomai@xenomai.org
Subject: [Xenomai-core] Re: [syscall.c] rt_bind_queue/heap()
Date: Mon, 10 Oct 2005 13:42:01 +0200	[thread overview]
Message-ID: <434A5389.2060905@domain.hid> (raw)
In-Reply-To: <OF67718347.A739127D-ONC1257096.003D7ADA-C1257096.003F7677@domain.hid>

Dmitry Adamushko wrote:
> Philippe Gerum <rpm@xenomai.org> wrote on 10.10.2005 13:09:13:
> 
>  > Dmitry Adamushko wrote:
>  > > Philippe Gerum <rpm@xenomai.org> wrote on 05.10.2005 14:13:07:
>  > >
>  > >  >
>  > >  > Your patch is ok, my implementation was uselessly convoluted.
>  > >
>  > > Ok, then it's enclosed.
>  > >
>  > > 2005-10-05  Dmitry Adamushko  <dmitry.adamushko@domain.hid>
>  >
>  > Applied, thanks.
>  > ...
> 
> btw,
> 
> It looks like something wrong with the xenomai mailing list. I have got 
> your answer but only one copy (you specified my own e-mail) and I 
> haven't got my own message on the list (but I've cc'ed "xenomai-core").
>

Your mail to the list was blocked since you used an unregistered address to send 
it (datacon.at).

> One more thing. I had a discussion with Steven Seeger regarding the use 
> of NULL-named objects from the user space. I cc'ed you but probably you 
> were too buzy at that time. The problem is that one may create 
> successfully a NULL-named object but then there is no way to use it 
> since all further calls give an error (some funny stuff there indeed :)
> 
> So a simple fix would look like:
> 
> for all rt_OBJECT_create() calls in libnative:
> 
> int rt_mutex_create(RT_MUTEX *mutex, const char *name)
> {
> 
> + if (!name)
> + return -E_SOMETHING; // E_INVAL?
> 
> return XENOMAI_SKINCALL2(__xeno_muxid,
> __xeno_mutex_create,
> mutex,
> name);
> }
> 
> What do you think? Or are there any reasons to keep it as is now?
> 

The reason is to allow anonymous objects to be created, so that the descriptor 
could only be shared by tasks belonging to the same address space if they happen 
to all have access to the descriptor's memory. Kind of semi-private object if 
you want. The fact that such an object is non-bindable should not make it 
unusable actually.

> 
> p.s. I have cc'ed "xenomai@xenomai.org" for both reasons to test the 
> mailing list and, well, maybe someone else has an opinion on the matter.
> 
> 
>  > --
>  >
>  > Philippe.
> 
> ---
> Best regards,
> Dmitry
> 


-- 

Philippe.


  reply	other threads:[~2005-10-10 11:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <434A4BD9.1030407@domain.hid>
2005-10-10 11:33 ` [Xenomai-core] Re: [syscall.c] rt_bind_queue/heap() Dmitry Adamushko
2005-10-10 11:42   ` Philippe Gerum [this message]
2005-10-10 11:50 Dmitry Adamushko
2005-10-10 11:59 ` Philippe Gerum
2005-10-10 12:02 ` Philippe Gerum
2005-10-10 12:29   ` Dmitry Adamushko
2005-10-10 12:35     ` Philippe Gerum
2005-10-10 13:25       ` Dmitry Adamushko
2005-10-11  6:43       ` Dmitry Adamushko
2005-10-11  7:45         ` Philippe Gerum
2005-10-11 12:47           ` Dmitry Adamushko
2005-10-11 12:59             ` Philippe Gerum
2005-10-11 13:03               ` Philippe Gerum
2005-10-11  7:24       ` Jim Cromie

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=434A5389.2060905@domain.hid \
    --to=rpm@xenomai.org \
    --cc=dmitry.adamushko@domain.hid \
    --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.