linux-kernel - Re: [RFC PATCH 3/9] irq_work: Force raised irq work to run on irq work interrupt

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: <20140905135436.GA1715@lerouge>
Date:	Fri, 5 Sep 2014 15:54:38 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Catalin Iacob <iacobcatalin@...il.com>,
	Dave Jones <davej@...hat.com>, Ingo Molnar <mingo@...nel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC PATCH 3/9] irq_work: Force raised irq work to run on irq
 work interrupt

On Thu, Sep 04, 2014 at 05:40:20PM +0200, Peter Zijlstra wrote:
> On Thu, Sep 04, 2014 at 03:33:40PM +0200, Frederic Weisbecker wrote:
> > > Why not something like the below; then it becomes a compile time matter.
> > 
> > Problem is that some archs only have that information at runtime.
> > See x86 for example which tests cpu_has_apic.
> 
> So the other archs can still benefit, no? Also, on x86 cpu features can
> be used with asm_goto/jump_labels, your approach wrecks that too by
> copying it into some static variable, see static_cpu_has().

Ah I didn't know about that static_cpu_has().
I'm going to try the way you suggest then.

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