|
Is there a way to print the type of request (read or write) being added to Thank You. |
Replies: 3 comments 1 reply
|
You can modify the code in the analysis folder to support printing the type of requests. |
|
Is this issue not related to the updates made to the TranslationReq struct in akita/mem/vm/protocol.go? I'm trying to identify requests being added to walkingTranslations (mmu.go) |
|
I guess what you are asking is to identify the original read/write request that triggers a migration, right? There are two possible methods. One is to add a details field in the translation request, which should have type The second method is more difficult but may require less intrusive code modification. You can create a tracer that applies to the address translator, TLBs, and MMU. Since the tasks are organized in a tree hierarchy, you can always back trace to the original memory access request. You can check our visualization tracer as an example. |
|
Thank you! It's working now. 😊 |
I guess what you are asking is to identify the original read/write request that triggers a migration, right?
There are two possible methods. One is to add a details field in the translation request, which should have type
map[string]any. Then, for every time when you creat a translation request, you can carry the memory access request.The second method is more difficult but may require less intrusive code modification. You can create a tracer that applies to the address translator, TLBs, and MMU. Since the tasks are organized in a tree hierarchy, you can always back trace to the original memory access request. You can check our visualization tracer as an example.