Re: [1/3] powerpc: Don't preempt_disable() in show_cpuinfo()

2018-01-17 Thread Michael Ellerman
On Wed, 2018-01-10 at 06:10:12 UTC, Benjamin Herrenschmidt wrote: > This causes warnings from cpufreq mutex code. This is also > rather unnecessary and ineffective. If we really want to > prevent concurrent unplug, we could take the unplug read > lock but I don't see this being critical. > > Signe

Re: [1/3] powerpc: Don't preempt_disable() in show_cpuinfo()

2018-01-15 Thread Michael Ellerman
On Wed, 2018-01-10 at 06:10:12 UTC, Benjamin Herrenschmidt wrote: > This causes warnings from cpufreq mutex code. This is also > rather unnecessary and ineffective. If we really want to > prevent concurrent unplug, we could take the unplug read > lock but I don't see this being critical. > > Signe

[PATCH 1/3] powerpc: Don't preempt_disable() in show_cpuinfo()

2018-01-09 Thread Benjamin Herrenschmidt
This causes warnings from cpufreq mutex code. This is also rather unnecessary and ineffective. If we really want to prevent concurrent unplug, we could take the unplug read lock but I don't see this being critical. Signed-off-by: Benjamin Herrenschmidt --- arch/powerpc/kernel/setup-common.c | 11