From: "André Tousch" <andre.tousch@domain.hid>
To: adeos-main@gna.org
Subject: [Adeos-main] __adeos_handle_event
Date: Tue, 19 Oct 2004 15:10:34 +0200 [thread overview]
Message-ID: <008b01c4b5dd$04d20890$7405a8c0@domain.hid> (raw)
In-Reply-To: <1097614490.672.6.camel@domain.hid>
Hi,
I'm currently using Adeos 2.4/armnommu to run an RTOS with Linux.
It works well but I have a problem with events.
I use __adeos_handle_event(ADEOS_USER_EVENT, &event) to send information
from Linux to the RTOS.
Reciprocally, I use adeos_propagate_irq(IRQ_A) to send information from
the RTOS to Linux.
Now I have the following scenario: Linux sends an event to the RTOS,
which replies from the event handler by propagating an IRQ.
1) Linux does __adeos_handle_event(ADEOS_USER_EVENT). Domain switches to
RTOS
2) RTOS handles the event. It adeos_propagate_irq()'s to Linux.
3) RTOS does adeos_suspend_domain(). Domain switches back to Linux.
4) Linux runs from just after the context switch in
__adeos_handle_event(). No __adeos_sync_stage() is made, and the IRQ_A
handler is not called before next hardware IRQ.
Why is there no call to __adeos_sync_stage() in __adeos_handle_event()?
Or do I miss something?
Thanks for you support
Regards,
André Tousch
next prev parent reply other threads:[~2004-10-19 13:10 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 ` André Tousch [this message]
2004-10-19 14:37 ` [Adeos-main] __adeos_handle_event Philippe Gerum
2004-10-19 14:43 ` Philippe Gerum
2004-12-10 10:05 ` [Adeos-main] End of interrupt scheduling Andre Tousch
2004-12-10 12:36 ` 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='008b01c4b5dd$04d20890$7405a8c0@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.