@@ -37,6 +37,8 @@ toc::[]
37
37
The most important functionality of this repository is the `--china` option, sample usage:
38
38
39
39
....
40
+ python3 -m venv .venv
41
+ . .venv/bin/activate
40
42
./setup
41
43
./run --china > index.html
42
44
firefox index.html
@@ -121,6 +123,8 @@ Reserve 12Gb of disk and run:
121
123
....
122
124
git clone https://github.com/cirosantilli/linux-kernel-module-cheat
123
125
cd linux-kernel-module-cheat
126
+ python3 -m venv .venv
127
+ . .venv/bin/activate
124
128
./setup
125
129
./build --download-dependencies qemu-buildroot
126
130
./run
@@ -177,6 +181,8 @@ All available modules can be found in the link:kernel_modules[] directory.
177
181
It is super easy to build for different <<cpu-architecture,CPU architectures>>, just use the `--arch` option:
178
182
179
183
....
184
+ python3 -m venv .venv
185
+ . .venv/bin/activate
180
186
./setup
181
187
./build --arch aarch64 --download-dependencies qemu-buildroot
182
188
./run --arch aarch64
@@ -660,6 +666,8 @@ For the most part, if you just add the `--emulator gem5` option or `*-gem5` suff
660
666
If you haven't built Buildroot yet for <<qemu-buildroot-setup>>, you can build from the beginning with:
661
667
662
668
....
669
+ python3 -m venv .venv
670
+ . .venv/bin/activate
663
671
./setup
664
672
./build --download-dependencies gem5-buildroot
665
673
./run --emulator gem5
@@ -726,6 +734,8 @@ For example, to do a <<qemu-buildroot-setup>> inside Docker, run:
726
734
727
735
....
728
736
sudo apt-get install docker
737
+ python3 -m venv .venv
738
+ . .venv/bin/activate
729
739
./setup
730
740
./run-docker create && \
731
741
./run-docker sh -- ./build --download-dependencies qemu-buildroot
@@ -877,6 +887,8 @@ Or to run a baremetal example instead:
877
887
Be saner and use our custom built QEMU instead:
878
888
879
889
....
890
+ python3 -m venv .venv
891
+ . .venv/bin/activate
880
892
./setup
881
893
./build --download-dependencies qemu
882
894
./run
@@ -1134,6 +1146,8 @@ You can install those libraries with:
1134
1146
1135
1147
....
1136
1148
cd linux-kernel-module-cheat
1149
+ python3 -m venv .venv
1150
+ . .venv/bin/activate
1137
1151
./setup
1138
1152
./build --download-dependencies userland-host
1139
1153
....
@@ -1313,6 +1327,8 @@ Every `.c` file inside link:baremetal/[] and `.S` file inside `baremetal/arch/<a
1313
1327
For example, to run link:baremetal/arch/aarch64/dump_regs.c[] in QEMU do:
1314
1328
1315
1329
....
1330
+ python3 -m venv .venv
1331
+ . .venv/bin/activate
1316
1332
./setup
1317
1333
./build --arch aarch64 --download-dependencies qemu-baremetal
1318
1334
./run --arch aarch64 --baremetal baremetal/arch/aarch64/dump_regs.c
@@ -1397,6 +1413,8 @@ You can run all the baremetal examples in one go and check that all assertions p
1397
1413
To use gem5 instead of QEMU do:
1398
1414
1399
1415
....
1416
+ python3 -m venv .venv
1417
+ . .venv/bin/activate
1400
1418
./setup
1401
1419
./build --download-dependencies gem5-baremetal
1402
1420
./run --arch aarch64 --baremetal userland/c/hello.c --emulator gem5
@@ -1475,6 +1493,8 @@ For development, you will want to do a more controlled build with extra error ch
1475
1493
For the initial build do:
1476
1494
1477
1495
....
1496
+ python3 -m venv .venv
1497
+ . .venv/bin/activate
1478
1498
./setup
1479
1499
./build --download-dependencies docs
1480
1500
....
@@ -3964,6 +3984,8 @@ Then, from inside that image:
3964
3984
sudo apt-get install git
3965
3985
git clone https://github.com/cirosantilli/linux-kernel-module-cheat
3966
3986
cd linux-kernel-module-cheat
3987
+ python3 -m venv .venv
3988
+ . .venv/bin/activate
3967
3989
./setup -y
3968
3990
....
3969
3991
@@ -26926,41 +26948,6 @@ https://www.samsung.com/semiconductor/dram/module/M471A2K43BB1-CRC/ (http://web.
26926
26948
26927
26949
https://www.amazon.co.uk/Samsung-DDR4-16-GB-DDR4-2400-MHz-Memory-Module/dp/B016N24XKQ (http://web.archive.org/web/20181224203214/https://www.amazon.co.uk/Samsung-DDR4-16-GB-DDR4-2400-MHz-Memory-Module/dp/B016N24XKQ[archive]) 355.43 UK Pounds for 2x 16 GiB.
26928
26950
26929
- ===== Samsung MZVLB512HAJQ-000L7 512GB SSD
26930
-
26931
- PCIe TLC OPAL2.
26932
-
26933
- https://www.samsung.com/semiconductor/ssd/client-ssd/MZVLB512HAJQ/ (http://web.archive.org/web/20181224225400/https://www.samsung.com/semiconductor/ssd/client-ssd/MZVLB512HAJQ/[archive]).
26934
-
26935
- https://www.samsung.com/semiconductor/global.semi/file/resource/2018/05/PM981_M.2_SSD_Datasheet_v1.3_for_General.pdf | http://web.archive.org/web/20181224225410/https://www.samsung.com/semiconductor/global.semi/file/resource/2018/05/PM981_M.2_SSD_Datasheet_v1.3_for_General.pdf
26936
-
26937
- `sudo hdparm -Tt /dev/nvme0n1p5` on Ubuntu 20.04:
26938
-
26939
- ....
26940
- Timing cached reads: 29812 MB in 1.99 seconds = 15007.00 MB/sec
26941
- HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
26942
- Timing buffered disk reads: 6328 MB in 3.00 seconds = 2109.00 MB/sec
26943
- ....
26944
-
26945
- Nominal maximum sequential read speed: 3,000 MB/s
26946
-
26947
- ===== Seagate ST1000LM035-1RK1 1TB hard disk
26948
-
26949
- 1TB.
26950
-
26951
- https://www.disctech.com/Seagate-ST1000LM035-1TB-SATA-Hard-Drive 80 USD | http://web.archive.org/web/20181224201408/https://www.disctech.com/Seagate-ST1000LM035-1TB-SATA-Hard-Drive
26952
-
26953
- https://www.seagate.com/www-content/datasheets/pdfs/mobile-hddDS1861-2-1603-en_US.pdf | http://web.archive.org/web/20181225095438/https://www.seagate.com/www-content/datasheets/pdfs/mobile-hddDS1861-2-1603-en_US.pdf
26954
-
26955
- `sudo hdparm -Tt /dev/sda3` on Ubuntu 20.04:
26956
-
26957
- ....
26958
- Timing cached reads: 29594 MB in 1.99 seconds = 14893.89 MB/sec
26959
- Timing buffered disk reads: 386 MB in 3.01 seconds = 128.07 MB/sec
26960
- ....
26961
-
26962
- Nominal maximum speed: 140MB/s
26963
-
26964
26951
===== NVIDIA Quadro M1200 4GB GDDR5 GPU
26965
26952
26966
26953
=== Benchmark Internets
0 commit comments