linux-kernel - Re: [RFC][PATCH 1/8] sched,idle,alpha: Switch from TS_POLLING to TIF_POLLING

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: <5347FE56.5000206@twiddle.net>
Date:	Fri, 11 Apr 2014 07:38:14 -0700
From:	Richard Henderson <rth@...ddle.net>
To:	Peter Zijlstra <peterz@...radead.org>, mingo@...nel.org,
	tglx@...utronix.de, luto@...capital.net, nicolas.pitre@...aro.org,
	daniel.lezcano@...aro.org, umgwanakikbuti@...il.com
CC:	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 1/8] sched,idle,alpha: Switch from TS_POLLING to
 TIF_POLLING_NRFLAG

On 04/11/2014 06:42 AM, Peter Zijlstra wrote:
> Standardize the idle polling indicator to TIF_POLLING_NRFLAG such that
> both TIF_NEED_RESCHED and TIF_POLLING_NRFLAG are in the same word.
> This will allow us, using fetch_or(), to both set NEED_RESCHED and
> check for POLLING_NRFLAG in a single operation and avoid pointless
> wakeups.
> 
> Changing from the non-atomic thread_info::status flags to the atomic
> thread_info::flags shouldn't be a big issue since most polling state
> changes were followed/preceded by a full memory barrier anyway.
> 
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Andy Lutomirski <luto@...capital.net>
> Cc: Richard Henderson <rth@...ddle.net>
> Signed-off-by: Peter Zijlstra <peterz@...radead.org>
> ---
>  arch/alpha/include/asm/thread_info.h |    4 ++--
>  1 file changed, 2 inser

Acked-by: Richard Henderson <rth@...ddle.net>


r~
--
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/