summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2017-04-05 12:44:50 +1000
committerMichael Ellerman <mpe@ellerman.id.au>2017-04-13 23:37:17 +1000
commit40e275653e2cdb5be5aa828d31cc96eb0eef3346 (patch)
tree9f981f00ae7d9c0cc9b812de09b50cf3b3999880 /security
parentebbe9d7d3a2ca0d62f1a2c08c7e7a3e0a88cf999 (diff)
downloadlinux-stable-40e275653e2cdb5be5aa828d31cc96eb0eef3346.tar.gz
linux-stable-40e275653e2cdb5be5aa828d31cc96eb0eef3346.tar.bz2
linux-stable-40e275653e2cdb5be5aa828d31cc96eb0eef3346.zip
powerpc/powernv: Always enable SMP when building powernv
The powernv platform supports Power7 and later CPUs, all of which are multithreaded and multicore. As such we never build a SMP=n kernel for those machines, other than possibly for debugging or running in a simulator. In the debugging case we can get a similar effect by booting with nr_cpus=1, or there's always the option of building a custom kernel with SMP hacked out. For running in simulators the code size reduction from building without SMP is not particularly important, what matters is the number of instructions executed. A quick test shows that a SMP=y kernel takes ~6% more instructions to boot to a shell. Booting with nr_cpus=1 recovers about half that deficit. On the flip side, keeping the SMP=n kernel building can be a pain at times. And although we've mostly kept it building in recent years, no one is regularly testing that the SMP=n kernel actually boots and works well on these machines. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions