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

readme: typo

Browse Source
This commit is contained in:
Ciro Santilli
2018-04-17 13:16:33 +01:00
parent 02b433e3ee
commit ffa430eef9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.adoc
View File

@@ -4835,7 +4835,7 @@ Why so long? I had previously documented on README 10 minutes at: fb317f47786336
One methodology problem is that some gem5 and QEMU were run with different kernel configs, due to <<gem5-qemu-config>>. This could have been improved if we normalized by instruction counts, but to do that we would have to enable tracing which makes QEMU run much slower. One methodology problem is that some gem5 and QEMU were run with different kernel configs, due to <<gem5-qemu-config>>. This could have been improved if we normalized by instruction counts, but to do that we would have to enable tracing which makes QEMU run much slower.
But TODO: on aarch64 both use the same kernel build alrady, and the gem5 instruction count is much higher, why? But TODO: on aarch64 both use the same kernel build already, and the gem5 instruction count is much higher, why?
==== Benchmark initial build ==== Benchmark initial build