3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 02:05:57 +01:00
Code Issues Releases Wiki Activity

baremetal: only rebuild required files based on mtime

Browse Source 
Move multcore test up with bootloader.
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2018-11-22 00:00:03 +00:00
parent f73eaaffd2
commit 8dd01415f5
4 changed files with 99 additions and 93 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.adoc
View File

@@ -1589,7 +1589,9 @@ See also: https://github.com/cirosantilli/linux-kernel-module-cheat/issues/19
The implementation is described at: https://stackoverflow.com/questions/46415059/how-to-observe-aarch64-system-registers-in-qemu/53043044#53043044
=== GDB step debug multicore
=== GDB step debug multicore userland
For a more minimal baremetal multicore setup, see: <<arm-multicore>>.
We can set and get which cores the Linux kernel allows a program to run on with `sched_getaffinity` and `sched_setaffinity`:
@@ -10510,13 +10512,13 @@ output:
==== ARM multicore
TODO get working: CPU1 not waking up:
TODO get working: CPU 1 not waking up:
....
./run --arch aarch64 --baremetal arch/aarch64/no_bootloader/multicore
./run --arch aarch64 --baremetal arch/aarch64/multicore --cpus 2
....
Source: link:baremetal/arch/aarch64/no_bootloader/multicore.S[]
Source: link:baremetal/arch/aarch64/multicore.S[]
CPU 0 of this program enters a spinlock loop: it repeatedly checks if a given memory address is `1`.