From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2018-01-10 06:11:01
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 <benh@kernel.crashing.org>
---
arch/powerpc/kernel/setup-common.c | 11 -----------
1 file changed, 11 deletions(-)
@@ -242,14 +242,6 @@ static int show_cpuinfo(struct seq_file *m, void *v)unsignedshortmaj;unsignedshortmin;-/* We only show online cpus: disable preempt (overzealous, I-*knew)topreventcpugoingdown.*/-preempt_disable();-if(!cpu_online(cpu_id)){-preempt_enable();-return0;-}-#ifdef CONFIG_SMPpvr=per_cpu(cpu_pvr,cpu_id);#else
@@ -358,9 +350,6 @@ static int show_cpuinfo(struct seq_file *m, void *v)#ifdef CONFIG_SMPseq_printf(m,"\n");#endif--preempt_enable();-/* If this is the last cpu, print the summary */if(cpumask_next(cpu_id,cpu_online_mask)>=nr_cpu_ids)show_cpuinfo_summary(m);
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2018-01-10 06:10:49
We used to not put the newline between the CPU part and the summary
part on UP kernels. This is a rather pointless ifdef so take it out.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/powerpc/kernel/setup-common.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
@@ -346,10 +346,8 @@ static int show_cpuinfo(struct seq_file *m, void *v)loops_per_jiffy/(500000/HZ),(loops_per_jiffy/(5000/HZ))%100);#endif--#ifdef CONFIG_SMPseq_printf(m,"\n");-#endif+/* If this is the last cpu, print the summary */if(cpumask_next(cpu_id,cpu_online_mask)>=nr_cpu_ids)show_cpuinfo_summary(m);
From: Michael Ellerman <hidden> Date: 2018-01-15 10:16:20
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.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
From: Michael Ellerman <hidden> Date: 2018-01-17 13:25:56
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.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
From: Michael Ellerman <hidden> Date: 2018-01-17 13:30:26
On Wed, 2018-01-10 at 06:10:13 UTC, Benjamin Herrenschmidt wrote:
We used to not put the newline between the CPU part and the summary
part on UP kernels. This is a rather pointless ifdef so take it out.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>