All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: ?? <2hang.j1ng.home@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] RT ISR re-entrance
Date: Mon, 27 Aug 2007 12:32:32 +0200	[thread overview]
Message-ID: <46D2A840.8040301@domain.hid> (raw)
In-Reply-To: <10837d740708262338w2def2f9er8fd2ca589e681992@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

?? wrote:
> hi all,
> 
> In SMP system, an edge triggerred interrupt may be dispatched to multiple
> cpus, so the RT ISR of this interrupt may be involved on multiple cpus at
> the same time. The question comes: is RT ISR need to be reentrant as
> designed or do I miss something?

Good question. I would say: yes, it's the I-pipe user's job to take care
of re-entrance safety.

Vanilla Linux prevents this via the IRQ_INPROGRESS flag. Xenomai 2.4 and
since 2.3.2 achieves re-entrance protection for the registered driver
handler by holding the IRQ-related spinlock while calling into that
handler. Still, this isn't something the user should build his system
upon. It is rather recommended for determinism and efficiency reasons to
assign RT IRQs to a specific CPU.

HTH,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-08-27 10:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27  6:38 [Adeos-main] RT ISR re-entrance 张晶
2007-08-27 10:32 ` Jan Kiszka [this message]
2007-08-27 13:54   ` 张晶
2007-08-27 16:55     ` Jan Kiszka

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=46D2A840.8040301@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=2hang.j1ng.home@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.