linux-kernel - Re: [RFC PATCH 11/15] x86: Nohz task support

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: <1292918729.5021.195.camel@laptop>
Date:	Tue, 21 Dec 2010 09:05:29 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...e.hu>,
	Steven Rostedt <rostedt@...dmis.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Anton Blanchard <anton@....ibm.com>,
	Tim Pepper <lnxninja@...ux.vnet.ibm.com>
Subject: Re: [RFC PATCH 11/15] x86: Nohz task support

On Tue, 2010-12-21 at 02:30 +0100, Frederic Weisbecker wrote:
> On Mon, Dec 20, 2010 at 05:23:19PM +0100, Peter Zijlstra wrote:
> > On Mon, 2010-12-20 at 16:24 +0100, Frederic Weisbecker wrote:
> > > 
> > > Implement the thread flag, syscalls and exception hooks for
> > > nohz task support.
> > > 
> > 
> > I saw:
> >  - syscall
> >  - do_int3
> >  - do_debug (int1)
> >  - #PF
> > 
> > So where's all other interrupts?
> 
> No need to handle them.
> 
> We have:
> 
> rcu_irq_enter() rcu_irq_exit() rcu_nmi_enter() rcu_nmi_exit()
> and they already act as pauses into extended quiescent states, which
> is enough for our needs.

Oh, and RCU is the only thing you need to worry about is it?
--
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/