Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
* Reentrant Interrupt Handler
@ 2019-03-17  5:22 ksourav
  0 siblings, 0 replies; only message in thread
From: ksourav @ 2019-03-17  5:22 UTC (permalink / raw)
  To: kernelnewbies

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-17  5:22 Reentrant Interrupt Handler ksourav

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org kernelnewbies@archiver.kernel.org
	public-inbox-index kernelnewbies


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/ public-inbox