You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to do step 4 under 'Writing Your Own Wrapper of Ramulator 2.0 for my own Simulator' in readme file, to send the memory requests from my simulator to Ramulator 2.0.
Inside frontend.h file, ("virtual bool receive_external_requests(int req_type_id, Addr_t addr, int source_id, std::function<void(Request&)> callback) { return false; }"), it returns false and hence the memory requests are not sent properly to the ramulator.
Do I have to modify any files of the ramulator code base? Or do I have to make 2 separate files of MyWrapper.h and MyWrappr.cpp?
The text was updated successfully, but these errors were encountered:
I have an example SystemC frontend on my fork of this repo. It may be useful for your development, and feel free to reach out to me for help. It's in the Readme:
When you implement your own frontend that inherits from the frontend interface, your own implementation of this virtual function will override the default implementation in the interface class.
When you implement your own frontend that inherits from the frontend interface, your own implementation of this virtual function will override the default implementation in the interface class.
Is it convenient to provide a simple sample for demonstration?
I am trying to do step 4 under 'Writing Your Own Wrapper of Ramulator 2.0 for my own Simulator' in readme file, to send the memory requests from my simulator to Ramulator 2.0.
Inside frontend.h file, ("virtual bool receive_external_requests(int req_type_id, Addr_t addr, int source_id, std::function<void(Request&)> callback) { return false; }"), it returns false and hence the memory requests are not sent properly to the ramulator.
Do I have to modify any files of the ramulator code base? Or do I have to make 2 separate files of MyWrapper.h and MyWrappr.cpp?
The text was updated successfully, but these errors were encountered: