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

readme: more entry tidbits

Browse Source
This commit is contained in:
Ciro Santilli
2018-09-14 10:56:57 +01:00
parent 55765d7101
commit 5ed2fcb0ab
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.adoc
View File

@@ -279,7 +279,7 @@ Seriously though, if you want to be a real hardware hacker, it just can't be don
* link:https://en.wikipedia.org/wiki/Semiconductor_fabrication_plant[Silicon fabs] don't publish reveal their link:https://en.wikipedia.org/wiki/Design_rule_checking[design rules]
* which implies that there are no decent link:https://en.wikipedia.org/wiki/Standard_cell[standard cell libraries]. See also: https://www.quora.com/Are-there-good-open-source-standard-cell-libraries-to-learn-IC-synthesis-with-EDA-tools/answer/Ciro-Santilli
* which implies that people can't develop open source link:https://en.wikipedia.org/wiki/Electronic_design_automation[EDA tools]
* which implies that you can't get decent link:https://community.cadence.com/cadence_blogs_8/b/di/posts/hls-ppa-is-it-all-you-need-to-know[power performance and area] estimates
* which implies that you can't get decent link:https://community.cadence.com/cadence_blogs_8/b/di/posts/hls-ppa-is-it-all-you-need-to-know[power, performance and area] estimates
The only thing you can do with open source is purely functional designs with link:https://en.wikipedia.org/wiki/Verilator[Verilator], but you will never know if it can be actually produced and how efficient it can be.
@@ -309,9 +309,9 @@ link:https://en.wikipedia.org/wiki/QEMU[QEMU] is a system simulator: it simulate
QEMU is the leading cross arch system simulator as of 2018. It is even the default Android simulator that developers get with Android Studio 3 to develop apps without real hardware.
QEMU is also supported by Buildroot in-tree, see e.g.: https://github.com/buildroot/buildroot/blob/2018.05/configs/qemu_aarch64_virt_defconfig
QEMU is also supported by Buildroot in-tree, see e.g.: https://github.com/buildroot/buildroot/blob/2018.05/configs/qemu_aarch64_virt_defconfig We however just build our own manually with link:build-qemu[], as it gives more flexibility, and building QEMU is very easy!
All of this makes QEMU the natural choice of system simulator.
All of this makes QEMU the natural choice of default system simulator.
=== gem5 Buildroot setup
@@ -319,7 +319,7 @@ All of this makes QEMU the natural choice of system simulator.
This setup is like the <<qemu-buildroot-setup>>, but it uses link:http://gem5.org/[gem5] instead of QEMU as a system simulator.
QEMU tries to run as fast as possible and give correct results at the end, but it does not tell us how many CPU cycles it takes to do something, just the number of instructions it ran, and this cannot be used to estimate system performance. This is known as a functional simulation
QEMU tries to run as fast as possible and give correct results at the end, but it does not tell us how many CPU cycles it takes to do something, just the number of instructions it ran, and this cannot be used to estimate system performance. This is known as a functional simulation.
gem5 on the other hand, can simulate the system in more detail than QEMU, including:
@@ -335,7 +335,7 @@ See <<gem5-vs-qemu,like QEMU>> for a more thorough comparison.
==== gem5 Buildroot setup getting started
For the most part, if you just add the `--gem5` option or `-gem5` suffix to all commands and everything should magically work:
For the most part, if you just add the `--gem5` option or `*-gem5` suffix to all commands and everything should magically work:
....
./configure -g && \