From: Andre Tousch <andre.tousch@domain.hid>
To: adeos-main@gna.org
Subject: [Adeos-main] End of interrupt scheduling
Date: Fri, 10 Dec 2004 11:05:29 +0100 [thread overview]
Message-ID: <41B974E9.7080801@domain.hid> (raw)
In-Reply-To: <1098196994.666.11.camel@domain.hid>
Hi,
I'm currently using an RTOS with Linux/Adeos on ARM. The original
behaviour of the RTOS interrupt handler is:
- Lock interrupts
- Call high-level interrupt handler
- Unlock interrupts
- Schedule()
Adeos behaviour on sync_stage is:
- Stall domain
- Call interrupt handler
- Unstall Domain
If I want to imitate the original RTOS behaviour, I have to schedule
(RTOS scheduler) at end of interrupt.
I cannot do that in this domain's interrupt handler, since it would
Schedule() with domain stalled, and thus the domain would not receive
the interrupts until it gives control back to Adeos by suspending itself.
So the only way I've found to do that was to had a hook in Adeos which
would be called at sync_stage, just after interrupt handler call.
Thus the modified Adeos behaviour on sync_stage is:
- Stall domain
- Call interrupt handler
- Unstall Domain
- Call EndOfInterrupt Handler.
Now I have exactly the behaviour expected from my RTOS.
My question is, was there already a way to obtain this behaviour in Adeos?
Best regards,
André
next prev parent reply other threads:[~2004-12-10 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 9:28 [Adeos-main] Signalling virtual interrupts to higher priority domains Neugebauer Manfred
2004-10-12 20:59 ` Philippe Gerum
2004-10-19 13:10 ` [Adeos-main] __adeos_handle_event André Tousch
2004-10-19 14:37 ` Philippe Gerum
2004-10-19 14:43 ` Philippe Gerum
2004-12-10 10:05 ` Andre Tousch [this message]
2004-12-10 12:36 ` [Adeos-main] End of interrupt scheduling Michael Neuhauser
[not found] ` <41B9A304.6060101@domain.hid>
2004-12-10 13:52 ` Michael Neuhauser
2004-12-11 23:40 ` Philippe Gerum
2004-12-11 23:33 ` Philippe Gerum
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=41B974E9.7080801@domain.hid \
--to=andre.tousch@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.