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: fix some c++ -> that expands to crazy char

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-12-19 00:00:00 +00:00
parent 44bf3820f9
commit 7c6454e5c1
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.adoc
View File

@@ -13043,15 +13043,15 @@ if (curStaticInst && curStaticInst->isMemRef()) {
Fault fault = curStaticInst->execute(&t_info, traceData);
....
* `curStaticInst->isMemRef()` is true, and there is no instruction `execute` call in that part of the branch, only for instructions that don't touch memory
* `+curStaticInst->isMemRef()+` is true, and there is no instruction `execute` call in that part of the branch, only for instructions that don't touch memory
* `_status` is `BaseSimpleCPU::Status::DcacheWaitResponse` and `advanceInst` is not yet called
So, where is the `execute` happening? Well, I'll satisfy myself with a quick source grep and guess:
* `curStaticInst->initiateAcc` sets up some memory request events
* `+curStaticInst->initiateAcc+` sets up some memory request events
* which likely lead up to: `TimingSimpleCPU::completeDataAccess`, which off the bat ends in `advanceInst`.
+
It also calls `curStaticInst->completeAcc`, which pairs up with the `initiateAcc` call.
It also calls `+curStaticInst->completeAcc+`, which pairs up with the `initiateAcc` call.
===== gem5 event queue TimingSimpleCPU syscall emulation freestanding example analysis with caches