Re: [PATCH v3] watchdog: Fix a watchdog crash in some configurations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> +	if (tick_nohz_full_enabled()) {
> +		if (!cpumask_empty(tick_nohz_full_mask))
> +			pr_info("Disabling watchdog on nohz_full cores by default\n");
> +		cpumask_andnot(&watchdog_cpumask, cpu_possible_mask,
> +			       tick_nohz_full_mask);
> +	} else
> +		cpumask_copy(&watchdog_cpumask, cpu_possible_mask);

In case it's not clear, the only difference between v3 and v2 of this 
patch, is that v3 corrects the checkpatch.pl violations. (I apologize for 
the multiple emails required to get such a small patch perfected. I'll 
have the workflow going much smoother next time, I promise.)

>  
>  	if (watchdog_enabled)
>  		watchdog_enable_all_cpus();
> -- 
> 2.3.7
> 
> 

thanks,
John H.

--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux