Fix issues with ARMv6+v6k+v7 kernels
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest13 of 14 patches 0 repliesNew
13 of 14 patches are in this archive. The cover letter announces 14.
Patches in v1 No applies recorded yet
Reviews trailers per patch
8 of 13 patches have a Reviewed-by or Acked-by.
| Patch | Tony Lindgren |
|---|---|
| 1/14 | T-b |
| 2/14 | T-b |
| 3/14 | T-b |
| 4/14 | A-b |
| 7/14 | A-b |
| 8/14 | A-b |
| 9/14 | A-b |
| 10/14 | A-b |
| 11/14 | A-b |
| 11/14 | A-b |
| 12/14 | T-b |
| 13/14 | T-b |
| 14/14 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 00/14] Fix issues with ARMv6+v6k+v7 kernels
Quoted 21 lines · Russell King - ARM Linux
This patch series reworks the ARMv6/ARMv6K support options, code selection, and bit operations such that it's possible to safely build a kernel which supports ARMv6, ARMv6K, ARMv7 and ARMv7 SMP in one image.
Currently, we use
CPU_V6for both ARMv6 and ARMv6K, settingCPU_32v6Kif we have the K extensions.CPU_32v6Kdirectly controlled whether we should include the ARMv6K instructions (clrex, load/store exclusive byte, half-word, double). As the bitops code uses the load/store exclusive byte operations, unsettingCPU_32v6Kresults in these falling back to their non-SMP local-irq-disabling variants. These are only safe in uniprocessor environments.So, the first two patches convert the bitops to use the ARMv6 load/store exclusive word operations - and ensuring correctness by ensuring that the pointer passed in is word-aligned.
We then introduce a new
CPU_V6Kwhich indicates that we're including an ARMv6K CPU in the build, which frees upCPU_V6to mean that we're including an ARMv6 non-K CPU.
Quoted 6 lines
We can then use
CPU_V6to ensure that the non-v6K code paths which are still SMP safe are selected.Without this patch set, such a kernel will be unsafe when run on SMP platforms as it omits necessary SMP code to ensure that bit operations are safe.
Amazing, based on a quick test this series boots just fine on non-v6K omap2420 using omap2plus_defconfig :)
Tony