From: Philippe Gerum <rpm@xenomai.org>
To: Germain Olivier <germain.olivier@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Initialization of a nucleus pod
Date: Mon, 30 Jan 2006 00:00:46 +0100 [thread overview]
Message-ID: <43DD491E.7010601@domain.hid> (raw)
In-Reply-To: <1596.10.2.100.4.1137683264.squirrel@domain.hid>
Germain Olivier wrote:
> Thank you for your response
>
> So rootcb isn't the "scheduler task".
> I was thinking it was this task which was determining what thread to run,
> depending of its parameters (priority, periodicity, scheduling mode).
>
> I go back to the code to understand how it work ...
>
Use the simulator to understand the dynamics of this code: it brings you
single-stepping of the entire Xenomai core over GDB, at source code level.
> Germain
>
>
>>xnthread_init does part of the initialization. The low level part of
>>rootcb (its xnarchtcb_t member) is initialized twice, first by the call
>>to xnarch_init_tcb in xnthread_init, and then overriden by
>>xnarch_init_root_tcb in xnpod_init.
>>
>>For any other thread than root, the thread would be given a stack and
>>entry point by the call to xnarch_init_thread in xnpod_start_thread. But
>>the root thread is Xenomai idle task, a placeholder for whatever task
>>Linux is currenty running. At the time where xnpod_init is called, the
>>root thread is the current context, so already has a stack and is
>>already running.
>>
>>--
>>
>>
>> Gilles Chanteperdrix.
>>
>
>
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
>
--
Philippe.
prev parent reply other threads:[~2006-01-29 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 14:05 [Xenomai-core] Initialization of a nucleus pod Germain Olivier
2006-01-19 12:50 ` Gilles Chanteperdrix
2006-01-19 15:07 ` Germain Olivier
2006-01-29 23:00 ` Philippe Gerum [this message]
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=43DD491E.7010601@domain.hid \
--to=rpm@xenomai.org \
--cc=germain.olivier@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.