All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: ali hagigat <hagigatali@gmail.com>
Cc: Xenomai@xenomai.org
Subject: Re: [Xenomai] Can we have nested interrupt handling in Xenomai?
Date: Wed, 22 Aug 2012 10:59:57 +0200	[thread overview]
Message-ID: <50349F8D.3080102@xenomai.org> (raw)
In-Reply-To: <CAKKWdtei-4S1A_AyhAifj+HxuGcVCuNRsDUeytX=21=bB9UwbQ@mail.gmail.com>

On 08/22/2012 06:28 AM, ali hagigat wrote:
> Can we have nested interrupt handling in Xenomai? Suppose we are in
> the middle of an interrupt handler and a new interrupt comes in, CPU
> will start executing the handler of the new interrupt completely? or
> that interrupt is logged only for that domain to be serviced later?

No, we do not support nested interrupt. You should note that the Linux
kernel has stopped re-enabling hardware interrupts in the middle of the
interrupt handlers for some time now: if an interrupt handler takes a
long time to execute, then there is a bug in the interrupt handler. The
interrupt handler has to be fixed, re-enabling interrupts is a bad
workaround.

> 
> As far as I understood, when an interrupt comes, that interrupt is
> disabled and the domain pipeline is stalled and then the interrupt
> handler is called.
> When the interrupt handler returns, the domain pipeline is unstalled.
> Is that correct?

Not quite, it depends on which domain is current and which domain the
interrupt is for.

-- 
					    Gilles.


  reply	other threads:[~2012-08-22  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22  4:28 [Xenomai] Can we have nested interrupt handling in Xenomai? ali hagigat
2012-08-22  8:59 ` Gilles Chanteperdrix [this message]
2012-08-22  9:48   ` ali hagigat
2012-08-22 11:31     ` Gilles Chanteperdrix

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=50349F8D.3080102@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Xenomai@xenomai.org \
    --cc=hagigatali@gmail.com \
    /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.