From: Dmitry Adamushko <dmitry.adamushko@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: [Xenomai-core] Re: [syscall.c] rt_bind_queue/heap()
Date: Mon, 10 Oct 2005 14:29:59 +0200 [thread overview]
Message-ID: <b647ffbd0510100529v2c96d260r@domain.hid> (raw)
In-Reply-To: <434A585B.40905@domain.hid>
> As you noticed below, the point is that this feature should be active for
> kernel-based code only; for user-space, we're toast: typical chicken-and-egg
> problem since we need the registry to cross the space boundaries but the
> registry requires a name to index the object first. So yes, we need to check for
> anonymous calls in every service taking a symbolic name in native/syscalls.c,
> and return -EINVAL when applicable.
I thought that "libnative" would be a better place since this way we
would avoid the user mode -> kernel mode switch.
> ...Or, we might auto-generate some dummy name in native/syscalls.c we would pass
> to the registry when this situation arises, so that anonymous creation and use
> from user-space would still be possible.
Yep, in this case a name would be a string == object's address, thus
it's unique.
Ok, I'd probably vote for the 2-nd approach.
> --
>
> Philippe.
---
Best regards,
Dmitry
next prev parent reply other threads:[~2005-10-10 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 11:50 [Xenomai-core] Re: [syscall.c] rt_bind_queue/heap() Dmitry Adamushko
2005-10-10 11:59 ` Philippe Gerum
2005-10-10 12:02 ` Philippe Gerum
2005-10-10 12:29 ` Dmitry Adamushko [this message]
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
[not found] <434A4BD9.1030407@domain.hid>
2005-10-10 11:33 ` Dmitry Adamushko
2005-10-10 11:42 ` Philippe Gerum
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=b647ffbd0510100529v2c96d260r@domain.hid \
--to=dmitry.adamushko@domain.hid \
--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.