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]
Date:	Mon, 14 Apr 2014 12:52:05 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Viresh Kumar <viresh.kumar@...aro.org>, tglx@...utronix.de
CC:	linaro-kernel@...ts.linaro.org, linux-kernel@...r.kernel.org,
	fweisbec@...il.com, Arvind.Chauhan@....com,
	linaro-networking@...aro.org
Subject: Re: [PATCH 22/38] tick-sched: no need to recheck cpu_online() in
 can_stop_idle_tick()

On 04/14/14 09:23, Viresh Kumar wrote:
> We have already checked if 'cpu' is online or not and so don't need to recheck
> it.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>

Hm... doing some git archeology shows fa116ea35ec7 (nohz: no softirq
pending warnings for offline cpus, 2008-12-11), where the cpu_online()
check was added. Before that commit we already checked cpu_online()
similar to how the code is today. Perhaps we need to add a comment here?

> ---
>  kernel/time/tick-sched.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index 9cbba513..c81b6cf 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -716,7 +716,7 @@ static bool can_stop_idle_tick(int cpu, struct tick_sched *ts)
>  	if (need_resched())
>  		return false;
>  
> -	if (unlikely(local_softirq_pending() && cpu_online(cpu))) {
> +	if (unlikely(local_softirq_pending())) {
>  		static int ratelimit;
>  
>  		if (ratelimit < 10 &&


-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ