Date: Thu, 3 Dec 2015 23:33:14 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: Yunhong Jiang <yunhong.jiang@linux.intel.com>
cc: okuno.kohji@jp.panasonic.com, linux-kernel@vger.kernel.org
Subject: Re: Can we conditionally force threading irq with primary and thread
 handler?
In-Reply-To: <20151203191125.GA8945@jnakajim-build>
Message-ID: <alpine.DEB.2.11.1512032324410.4201@nanos>
References: <20151203191125.GA8945@jnakajim-build>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1061
Lines: 29

Yunhong,

On Thu, 3 Dec 2015, Yunhong Jiang wrote:

> 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 you want to avoid that the primary handler is force threaded, then
you can indicate that with IRQF_NO_THREAD.

Thanks,

	tglx


--
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/