Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1283281

Can we conditionally force threading irq with primary and thread handler?

Show all headers | View raw

Hi, Thomas
	On Commit 2a1d3ab8986d1b2 ("genirq: Handle force threading of irqs 
with primary and thread handler"), even if the caller of 
request_threaded_irq() provides a primary handler, that primary handler will 
be invoked in thread context. This may cause some latency issue for high 
real time requirement.

	I checked the discussion on https://lkml.org/lkml/2015/9/19/372 with 
Okuno and seems we need this change only if the irq is shared, otherwise, we 
can still use Okuno's mechanism, am I right? Do you think it's ok to force 
the primary handler for shared IRQ, otherwise, clear the IRQF_ONESHOT?

	If yes, I will cook a patch for it.

Thanks
--jyh

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Can we conditionally force threading irq with primary and thread  handler? Yunhong Jiang <yunhong.jiang@linux.intel.com> - 2015-12-03 20:30 +0100
  Re: Can we conditionally force threading irq with primary and thread  handler? Thomas Gleixner <tglx@linutronix.de> - 2015-12-03 23:40 +0100
    Re: Can we conditionally force threading irq with primary and thread  handler? Yunhong Jiang <yunhong.jiang@linux.intel.com> - 2015-12-04 00:00 +0100

csiph-web