* [Xenomai-core] Few questions xenomai schedule, for porting Therad, TCB for MIPS 4KeC
@ 2007-03-29 11:13 Andrew Xeno
2007-03-30 0:43 ` Jan Kiszka
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Xeno @ 2007-03-29 11:13 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]
Hello All,
This is my first mail on Xenomai, earIier I posted my messages on ADEOS
forum regarding IPIPE-1.0.5 porting on MIPS. Recently I started porting
Xenomai for the same architecture and could do some work related to
1. Xenomai Intialization of ROOT task
2. Timer and Interrupt related code.
3. XENO_SYSCALLS.
4. Trap Handlers
The Code changes are done considering MIPS 4KeC
Now
I could define Architecture related Task control block(TCB) user task,
active task, stack elements with inthe xnarchtcb_t.
Currently I am facing problem in creating and starting the task. After
understanding code flow, i could see that
Correct me if I am wrong!!!
1. When user calls "rt_task_create", the task state is defined as,
XNDORMANT, XNRELAX, XNSHADOW.
2. When user calls "rt_task_start", since the RTTASK being XNSHADOW,
xnpod_start_thread calls xnshadow_start and inturn resume which will remove
the task from the DORMANT state, however the XNRELAX state remains. This
makes sched->Ready queue being emptty. Later when xnpod_schedule is called,
since thread is not in the Ready queue and still remains in the RELAX mode,
xnpod_schedule exits from the context of "goto signal_unlock_and_exit;"
.Therefore this makes that my body of the new task not being executed.
Also I don't even see my "xnarch_init_thread" being called to intialize
startup functions for the new task. May I know when exactly this function is
called for the first newly created task.
I don't know where I am going wrong, few hints about xnpod_schedule on First
task creation will help me in verifying and debugging of my context swicth
code written fro this Architecture.
Regards
Andrew( Subbu)
[-- Attachment #2: Type: text/html, Size: 1811 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Xenomai-core] Few questions xenomai schedule, for porting Therad, TCB for MIPS 4KeC
2007-03-29 11:13 [Xenomai-core] Few questions xenomai schedule, for porting Therad, TCB for MIPS 4KeC Andrew Xeno
@ 2007-03-30 0:43 ` Jan Kiszka
0 siblings, 0 replies; 2+ messages in thread
From: Jan Kiszka @ 2007-03-30 0:43 UTC (permalink / raw)
To: Andrew Xeno; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Andrew Xeno wrote:
> Hello All,
> This is my first mail on Xenomai, earIier I posted my messages on ADEOS
> forum regarding IPIPE-1.0.5 porting on MIPS. Recently I started porting
> Xenomai for the same architecture and could do some work related to
> 1. Xenomai Intialization of ROOT task
> 2. Timer and Interrupt related code.
> 3. XENO_SYSCALLS.
> 4. Trap Handlers
> The Code changes are done considering MIPS 4KeC
[Not directly answering your question - but this would help to.]
This is now the third announcement of someone working on a MIPS port
[1,2]. Great news, definitely! But could we please
- roll out code (even if it's incomplete, utterly broken, targeting
different boards)
- create some branches or whatever repositories
- *work in public*
Then it should be far easier to discuss things, synchronise efforts,
avoid duplicate work (and pain...). Remember: the development model
makes open source so nice!
My 2 cents. :)
Jan
[1] https://mail.gna.org/public/xenomai-core/2007-03/msg00033.html
[2] https://mail.gna.org/public/xenomai-help/2007-03/msg00180.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-03-30 0:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-29 11:13 [Xenomai-core] Few questions xenomai schedule, for porting Therad, TCB for MIPS 4KeC Andrew Xeno
2007-03-30 0:43 ` Jan Kiszka
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.