From: Philippe Gerum <rpm@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] /proc/xenomai broken...
Date: Wed, 14 Jun 2006 18:31:40 +0200 [thread overview]
Message-ID: <449039EC.7070404@domain.hid> (raw)
In-Reply-To: <4490381F.6030309@domain.hid>
Philippe Gerum wrote:
> Gilles Chanteperdrix wrote:
>
>> Philippe Gerum wrote:
>> > Gilles Chanteperdrix wrote:
>> > > When using xenomai trunk, it appears that /proc/xenomai is no
>> longer a
>> > > directory but a file returning "0".
>> > > > > Check your recent changes for giving the nucleus a regular
>> syscall > table. I would not be surprised of some side-effect there.
>> i.e. > something going on with the xnptree_t descriptor?
>>
>> That is exactly the source of the problem, since iface_proc_root in
>> nucleus/module.c has not yet been set, the proc entry for the nucleus
>> interface get created directly under /proc instead of
>> /proc/xenomai/interfaces.
>>
>> Do we need a /proc entry for this interface ?
>>
>
> Not really. This would only give the exact number of processes bound to
> the nucleus, whilst major interface counters already display the number
> of bound threads.
>
This said, the other option would be to move the call to
xnshadow_mount() from the xnarch_init() to __xeno_sys_init() in a
kernel-only section, just after xnpod_init_proc() has returned. There is
nothing done in the arch-layer for any architecture that would prevent
this. Btw, I'd say that "core" would be better than "xenomai" to name
this internal interface.
--
Philippe.
next prev parent reply other threads:[~2006-06-14 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 15:59 [Xenomai-core] /proc/xenomai broken Gilles Chanteperdrix
2006-06-14 16:07 ` Philippe Gerum
2006-06-14 16:17 ` Gilles Chanteperdrix
2006-06-14 16:23 ` Philippe Gerum
2006-06-14 16:31 ` Philippe Gerum [this message]
2006-06-14 16:45 ` Gilles Chanteperdrix
2006-06-14 16:50 ` Philippe Gerum
2006-06-14 17:49 ` Gilles Chanteperdrix
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=449039EC.7070404@domain.hid \
--to=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.