powerpc: Don't preempt_disable() in show_cpuinfo()
PATCH 1/3 powerpc: Don't preempt_disable() in show_cpuinfo()
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.
--- arch/powerpc/kernel/setup-common.c | 11 ----------- 1 file changed, 11 deletions(-)
arch/powerpc/kernel/setup-common.c +0 -11
@@ -242,14 +242,6 @@ static int show_cpuinfo(struct seq_file *m, void *v)unsigned short maj;unsigned short min; -/* We only show online cpus: disable preempt (overzealous, I -* knew) to prevent cpu going down. */ -preempt_disable (); -if (!cpu_online (cpu_id)) { -preempt_enable (); -return 0 ; - } -#ifdef CONFIG_SMP pvr =per_cpu (cpu_pvr, cpu_id);#else
@@ -358,9 +350,6 @@ static int show_cpuinfo(struct seq_file *m, void *v)#ifdef CONFIG_SMP seq_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);
Signature · 1 line
2.14.3
PATCH 2/3 powerpc: Make newline in cpuinfo unconditional
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.
--- arch/powerpc/kernel/setup-common.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
arch/powerpc/kernel/setup-common.c +1 -3
@@ -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_SMP seq_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);
Signature · 1 line
2.14.3
Michael Ellerman
AppliedRe: [2/3] powerpc: Make newline in cpuinfo unconditional
Quoted 4 lines · Benjamin Herrenschmidt
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 <[email protected]>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/f5f563012a7002e64853c61d293d65
cheers
PATCH 3/3 powerpc: Cosmetic cleanup of cpuinfo_op
In reply to Benjamin Herrenschmidt--- arch/powerpc/kernel/setup-common.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
arch/powerpc/kernel/setup-common.c +4 -4
@@ -377,10 +377,10 @@ static void c_stop(struct seq_file *m, void *v) }const struct seq_operations cpuinfo_op = { - .start =c_start, - .next = c_next, - .stop = c_stop, - .show = show_cpuinfo, + .start = c_start, + .next = c_next, + .stop = c_stop, + .show = show_cpuinfo, };void __init check_for_initrd (void )
Signature · 1 line
2.14.3
Michael Ellerman
AppliedRe: [3/3] powerpc: Cosmetic cleanup of cpuinfo_op
Quoted 1 line · Benjamin Herrenschmidt
Signed-off-by Benjamin Herrenschmidt <[email protected]>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/fbadeb6bb1685f7a53869e240284ff
cheers
Michael Ellerman
AppliedQuoted 6 lines · 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 <[email protected]>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/349524bc0da698ec77f2057cf4a494
cheers
Michael Ellerman
AppliedQuoted 6 lines · 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 <[email protected]>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/349524bc0da698ec77f2057cf4a494
cheers