linux-kernel - Re: [PATCH -tip -v5] irq_work: generic hard-irq context callbacks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1284973981.2275.642.camel@laptop>
Date:	Mon, 20 Sep 2010 11:13:01 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	Huang Ying <ying.huang@...el.com>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	dhowells <dhowells@...hat.com>,
	Russell King <rmk@....linux.org.uk>,
	Kyle McMartin <kyle@...artin.ca>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	davem <davem@...emloft.net>,
	Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH -tip -v5] irq_work: generic hard-irq context callbacks

On Mon, 2010-09-20 at 14:20 +1000, Paul Mackerras wrote:
> On Fri, Sep 17, 2010 at 03:06:42PM +0200, Peter Zijlstra wrote:
> 
> > Provide a mechanism that allows running code in IRQ context. It is most
> > useful for NMI code that needs to interact with the rest of the system
> > -- like wakeup a task to drain buffers.
> > 
> > Perf currently has such a mechanism, so extract that and provide it as a
> > generic feature, independent of perf so that others may also benefit.
> > 
> > The IRQ context callback is generated through self-IPIs where possible,
> > or on architectures like powerpc which have soft-disabled IRQs, its ran
> > on the soft-enable path.
> 
> Actually these days we do it by setting the decrementer (the built-in
> timer facility) to generate an interrupt immediately (well, within one
> timebase tick, i.e. a small number of nanoseconds).

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