linux-kernel - Re: [patch-mm 01/23] NOHZ: Fix ARM,SH,SPARC64 idle nohz handling

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 11 Jun 2007 14:32:09 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>,
	Ingo Molnar <mingo@...e.hu>, Andi Kleen <ak@...e.de>,
	Arjan van de Ven <arjan@...radead.org>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	Chris Wright <chrisw@...s-sol.org>,
	Adam Belay <abelay@...ell.com>, Len Brown <lenb@...nel.org>,
	Dave Miller <davem@...emloft.net>,
	Russell King <rmk+kernel@....linux.org.uk>
Subject: Re: [patch-mm 01/23] NOHZ: Fix ARM,SH,SPARC64 idle nohz handling

On Mon, Jun 11, 2007 at 07:20:59AM +0200, Thomas Gleixner wrote:
> On Mon, 2007-06-11 at 09:26 +0900, Paul Mundt wrote:
> >
> > There are two paths here depending on hlt/nohlt setting, we need to have
> > tick_nohz_stop_sched_tick() for the TIF_POLLING_NRFLAG case, too.
> 
> Do you really want to run through that in every loop iteration ? If you
> have nohlt, then nohz is rather pointless.
> 
Well, nohlt is a corner case, but even so, nohz doesn't really make much
sense in the polling case. tick_nohz_restart_sched_tick() is also safe in
either path, so let's just go with your original patch. Sorry for the noise.

Acked-by: Paul Mundt <lethal@...ux-sh.org>
-
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/