-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AT model #9
Comments
Hello Matthias, thank you for your interes on this project. Currently I'm evaluating what I should add to the simulator and write some roadmap. Thank you! Màrius |
Yeah this is actually the reason why I'm asking: we have a AT DRAM model, because for precise modelling of DRAM you need AT. An LT DRAM model makes no sense at all. Here is the link to our DRAM and DRAM controller model DRAMSys: https://github.com/tukl-msd/DRAMSys |
I think I can add a AT model just writing a new MemoryInterface module using AT. The easiest way would be that each function (writeDataMem / readDataMem) perform one single entire transaction before return (no transaction pipelinin). |
You can take a look at https://github.com/mariusmm/RISC-V-TLM/blob/AT/src/MemoryInterfaceAT.cpp where there is a basic and dirty implementation. |
I think this would not make much of a difference to LT, because a real core would do transaction pipelining. I think this behaviour is more less the same as the blocking transport. The core could not exploit the memory system efficiently. However, if we model maybe many in-order cores then this could make already some sense 👍 |
I want to finish my master thesis based on at model, but not found any related project to learn |
You provide an LT model, is an AT model for more detailed performance analysis also on your roadmap?
The text was updated successfully, but these errors were encountered: