Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1283424
| Path | csiph.com!news.mixmin.net!news.albasani.net!news.mb-net.net!open-news-network.org!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | Thomas Gleixner <tglx@linutronix.de> |
| Newsgroups | linux.kernel |
| Subject | Re: Can we conditionally force threading irq with primary and thread handler? |
| Date | Thu, 03 Dec 2015 23:40:01 +0100 |
| Message-ID | <qBKHD-2Fu-1@gated-at.bofh.it> (permalink) |
| References | <qBHJN-QO-35@gated-at.bofh.it> |
| X-Original-To | Yunhong Jiang <yunhong.jiang@linux.intel.com> |
| User-Agent | Alpine 2.11 (DEB 23 2013-08-11) |
| MIME-Version | 1.0 |
| Content-Type | TEXT/PLAIN; charset=US-ASCII |
| X-Linutronix-Spam-Score | -1.0 |
| X-Linutronix-Spam-Level | - |
| X-Linutronix-Spam-Status | No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001,URIBL_BLOCKED=0.001 |
| Sender | robomod@news.nic.it |
| List-ID | <linux-kernel.vger.kernel.org> |
| X-Mailing-List | linux-kernel@vger.kernel.org |
| Approved | robomod@news.nic.it |
| Lines | 29 |
| Organization | linux.* mail to news gateway |
| X-Original-Cc | okuno.kohji@jp.panasonic.com, linux-kernel@vger.kernel.org |
| X-Original-Date | Thu, 3 Dec 2015 23:33:14 +0100 (CET) |
| X-Original-Message-ID | <alpine.DEB.2.11.1512032324410.4201@nanos> |
| X-Original-References | <20151203191125.GA8945@jnakajim-build> |
| X-Original-Sender | linux-kernel-owner@vger.kernel.org |
| Xref | csiph.com linux.kernel:1283424 |
Show key headers only | View raw
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/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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