From: Philippe Gerum <rpm@xenomai.org>
To: aaron durbin <aarondurbin@domain.hid>
Cc: "'adeos-main@gna.org'" <adeos-main@gna.org>
Subject: Re: [Adeos-main] adeos_enter/exit_syscall
Date: Thu, 05 Aug 2004 00:24:44 +0200 [thread overview]
Message-ID: <1091658284.618.149.camel@domain.hid> (raw)
In-Reply-To: <0C53F2DBA565D411885300508B553B5204CCEAE9@domain.hid>
On Thu, 2004-08-05 at 00:16, aaron durbin wrote:
> I have a question concerning the adeos_enter_syscall routine. Is there
> normally event monitors for syscall entry (SYSCALL_PROLOGUE)?
Not normally when no domain is loaded. The Linux domain by itself does
not intercept (its own) syscalls. But other domains might want this
(RTAI does).
> If so and
> handle_event returns non-zero then one automatically restores the registers
> and returns w/o calling the system call. Doesn't this destroy the call?
>
It prevents its execution by the Linux kernel actually. Think of a more
prioritary (in the sense higher in the pipeline than Linux) that wants
to intercept some specific syscalls issued by regular Linux apps, and
provides a replacement for them. In such a case, you might not want the
original syscall to be handled by Linux too; so you make sure that it is
not propagated to Linux -- this translates in having handle_event return
non-zero (because adeos_propagate_event is not called for the said
syscall in the upper domain handler).
> -Aaron
>
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main
--
Philippe.
next prev parent reply other threads:[~2004-08-04 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 22:16 [Adeos-main] adeos_enter/exit_syscall aaron durbin
2004-08-04 22:24 ` Philippe Gerum [this message]
2004-08-04 22:27 ` Marc Kleine-Budde
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=1091658284.618.149.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=aarondurbin@domain.hid \
--cc=adeos-main@gna.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.