Skip to content
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

Writing Your Own Wrapper of Ramulator 2.0 for my own Simulator #37

Open
prapti02 opened this issue Feb 10, 2024 · 3 comments
Open

Writing Your Own Wrapper of Ramulator 2.0 for my own Simulator #37

prapti02 opened this issue Feb 10, 2024 · 3 comments

Comments

@prapti02
Copy link

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?

@ankenman
Copy link

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:

https://github.com/ankenman/ramulator2

@RichardLuo79
Copy link
Collaborator

Hi,

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.

@Learn2006
Copy link

Hi,

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants