From: Philippe Gerum <rpm@xenomai.org>
To: barbalace@domain.hid
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] ppc Linux(root-domain) syscall
Date: Sun, 17 Dec 2006 19:27:11 +0100 [thread overview]
Message-ID: <1166380031.7818.19.camel@domain.hid> (raw)
In-Reply-To: <1166378947.458587c3ef22e@domain.hid>
On Sun, 2006-12-17 at 19:09 +0100, barbalace@domain.hid wrote:
> Reading Adeos patch (adeos-ipipe-2.6.14-ppc-1.3-05.patch) I see that after a
> 0xc00 (System call) is issued entry.S call __ipipe_syscall_root; this one in
> arch/ppc/kernel/ipipe-root.c dispatch the event and after this return
> eventually DoSyscall is executed if __ipipe_syscall_root return 0.
> If I don't missunderstand the code why not execute DoSyscall in the event
> dispatching?
Because you don't want to run all the code present in DoSyscall when you
don't run over the Linux domain, and the system call entry point may be
invoked from a non-Linux context, e.g. some RTOS running in parallel.
In the latter case, __ipipe_syscall root may return non-zero,
specifically 1 or -1.
The former means "the last syscall was not a Linux one, please forget
completly and exit", and the latter means "this was not a Linux syscall,
but it might have changed something Linux should be aware of, so check
for pending signals, rescheduling opportunities etc.". This is how
Xenomai interposes on all syscalls issued from a RT task in user-space,
and dispatches them depending on who wants to process it (i.e. the RTOS
kernel first, and eventually Linux if applicable).
>
> Thanks
> Antonio
>
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main
--
Philippe.
prev parent reply other threads:[~2006-12-17 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 18:09 [Adeos-main] ppc Linux(root-domain) syscall barbalace
2006-12-17 18:27 ` 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=1166380031.7818.19.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=barbalace@domain.hid \
/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.