CPU hotplug support for Versatile platforms
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] CPU hotplug support for Versatile platforms
Quoted 9 lines · Russell King - ARM Linux
Quoted 7 lines · Rob Herring
The platform specific SMP code is one area that prevents supporting a single kernel image. All the functions in
platsmp.cneed to be converted to function pointers and a lot of that code is pretty simliar across platforms. What's needed is a commonplatsmp.cwith something like platform specificsmp_opslike PowerPC. I think addressing that first would simplify this restructuring as you are doing some of what's needed, but you introducing new namespace problems like platform_cpu_*.
Quoted 7 lines
The split between
smp.candplatsmp.cis there to allow different SMP implementations from the standard ARM Ltd SMP implementation (and there will be different implementations.)Just because all the SMP implementations that are currently merged are the standard ARM Ltd SMP implementation does not mean that we should move stuff out of
platsmp.cinto the generic code.
Agreed, but the interface between smp.c and platsmp.c does not allow for more than one SMP platform in a single image. Granted, there are plenty of other obstacles to multi-platform kernel binaries, but this one would be good to address before there are a bunch of SMP platforns rather than after. Ideally, platsmp.c could be common, but optional for platforms that are significantly different.
The idea I have is add a smp_init function ptr to struct mdesc which would fill in an smp_ops struct of function pointers and call set_cpu_possible for each core. This would replace the direct smp_init_cpus call.
Rob