From: Jan Kiszka <jan.kiszka@domain.hid>
To: "kapilkumar.jain" <kapilkumar.jain@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Interrupt Sharing
Date: Wed, 09 Jan 2008 16:57:39 +0100 [thread overview]
Message-ID: <4784EEF3.2090906@domain.hid> (raw)
In-Reply-To: <014d01c852bc$5d4bff10$2903050a@domain.hid>
kapilkumar.jain wrote:
> Dear Mr. Jan Kiszka
>
> Long before i have asked solution for Interrupt sharing problem between non real time & real time module,
> as i have found it is difficult to disable the non real time.
>
> I have found the solution by return RTDM_IRQ_NONE | XN_ISR_PROPAGATE. from the ISR.
That's not a solution, it's a fragile workaround: Your RT device's IRQ
may suffer from priority inversion when an IRQ event for the non-RT side
is pending but cannot be handled timely (due to Linux stalling its IRQs
or some low-prio RT thread is blocking Linux). Then succeeding IRQ
events for the RT side will also have to wait until the non-RT side has
completed its processing.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-01-09 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 12:37 [Xenomai-core] Interrupt Sharing kapilkumar.jain
2008-01-09 15:57 ` Jan Kiszka [this message]
2008-01-10 4:16 ` kapilkumar.jain
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=4784EEF3.2090906@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=kapilkumar.jain@domain.hid \
--cc=xenomai@xenomai.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.