On 10/10/05, Philippe Gerum [EMAIL PROTECTED] wrote:
Dmitry Adamushko wrote:
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
Philippe Gerum wrote:
Dmitry Adamushko wrote:
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
Dmitry Adamushko wrote:
On 10/10/05, Philippe Gerum [EMAIL PROTECTED] wrote:
Dmitry Adamushko wrote:
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
Dmitry Adamushko wrote:
On 11/10/05, Philippe Gerum [EMAIL PROTECTED] wrote:
...
So,
1) don't display such names in /proc;
2) make a common mechanism for both spaces.
rt_mutex_create() // for other objects as well
{
...
- xnobject_copy_name(mutex-name,name);
Philippe Gerum wrote:
Dmitry Adamushko wrote:
On 11/10/05, Philippe Gerum [EMAIL PROTECTED] wrote:
...
So,
1) don't display such names in /proc;
2) make a common mechanism for both spaces.
rt_mutex_create() // for other objects as well
{
...
- xnobject_copy_name(mutex-name,name);
Dmitry Adamushko wrote:
Philippe Gerum [EMAIL PROTECTED] wrote on 10.10.2005 13:09:13:
Dmitry Adamushko wrote:
Philippe Gerum [EMAIL PROTECTED] wrote on 05.10.2005 14:13:07:
Your patch is ok, my implementation was uselessly convoluted.
Ok, then it's enclosed.
Philippe Gerum [EMAIL PROTECTED] wrote on 10.10.2005 13:09:13:
Dmitry Adamushko wrote:
Philippe Gerum [EMAIL PROTECTED] 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 [EMAIL
Dmitry Adamushko wrote:
snip
So it must be fixed. There must be an explicit prohibition on creating
NULL-named objects from the user-mode.
...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
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
Dmitry Adamushko wrote:
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
On 10/10/05, Philippe Gerum [EMAIL PROTECTED] wrote:
Dmitry Adamushko wrote:
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
11 matches
Mail list logo
