kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ksourav <sourav.jb1988@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Reentrant Interrupt Handler
Date: Sun, 17 Mar 2019 10:52:22 +0530	[thread overview]
Message-ID: <CAAJhNetO7_UND85E=34f04SjFpGC2Qy=frPSb8=bdZnfkQfpjA@mail.gmail.com> (raw)

Hi,
AFAIK, when cpu run an interrupt handler, local interrupt is disabled.
It means that this cpu is not going to be interrupted until it
executes the current interrupt handler. Can same interrupt occur on
other cpus?
Suppose a device interrupts and its handler starts running  on cpu0.
What happens if this device issue another interrupt before the handler
running on cpu0 is finished? Will interrupt handler run on another
(say cpu1) concurrently?  Any explanation regarding arm/gic will
helpful. Thanks in advance!

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

                 reply	other threads:[~2019-03-17  5:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAAJhNetO7_UND85E=34f04SjFpGC2Qy=frPSb8=bdZnfkQfpjA@mail.gmail.com' \
    --to=sourav.jb1988@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).