aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2024-10-31 13:56:30 +0200
committerKimplul <kimi.h.kuparinen@gmail.com>2024-11-01 10:27:56 +0200
commit576e73d39d89cf59e5a26fd3f3e9e6787578025d (patch)
tree5e70f793c088f87431abc0c953c5ec083d2631ab
parentd5e5afae9249da312b417bc4f5f45ac164404846 (diff)
downloadkmi-576e73d39d89cf59e5a26fd3f3e9e6787578025d.tar.gz
kmi-576e73d39d89cf59e5a26fd3f3e9e6787578025d.zip
add note about running on real hardware
-rw-r--r--docs/visionfive2.md13
1 files changed, 10 insertions, 3 deletions
diff --git a/docs/visionfive2.md b/docs/visionfive2.md
index 1e21896..60317b3 100644
--- a/docs/visionfive2.md
+++ b/docs/visionfive2.md
@@ -15,9 +15,7 @@ serial and ethernet booting, but I haven't looked into how they work.
The SD card should have an empty GPT table, you can create one with
`fdisk /dev/sdX/`.
-1. Build `kmi` with `GENERIC_UBOOT=1`. At the moment, SMP is broken on the
- VisionFive2, so you'll need to comment out `smp_bringup(d, fdt);` in
- `main.c`.
+1. Build `kmi` with `GENERIC_UBOOT=1`.
2. Create three partitions on an SD card of your choice:
```
@@ -75,3 +73,12 @@ the end address or the size of the `initrd`.
It should be possible to add the above commands to a script to run
automatically, though I haven't personally done this yet.
+
+## Note about running benchmarks on real hardware
+
+Currently there's only a single Big Kernel Lock, which is taken by cores when
+they are brought up. This means that if you run a benchmark from `benchmarks/`
+'directly' (`START()` needs some extra accomodations to properly handle the
+extra threads), the benchmark will spend a lot of its time waiting for other
+cores to start running, which has a significant impact on the results. I would
+suggest (for now) to just comment out `smp_bringup` in `main`.