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

Generalize the interface to the NC Verilog Simulator #1

Open
atsmith3 opened this issue May 24, 2020 · 0 comments
Open

Generalize the interface to the NC Verilog Simulator #1

atsmith3 opened this issue May 24, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@atsmith3
Copy link
Owner

atsmith3 commented May 24, 2020

Currently the NC Verilog Simulator is set up to model the entire device as a single restive load based on McPAT calculations. In order to model the power delivery network for modern large many core devices, The Verilog model and the interface shared memory interface should be dynamic based on the number of cores in the device.

This is easy to do from the verilog side as the VPI routines are recompiled at the time of running, however because the interface is shared memory and cannot use any C++ containers, it can just be statically allocated at Gem5 compile to use 256 entries for a maximum of 256 cores.

The files for this interface can be found in the src/python/pybind11/ and src/python/m5/

@atsmith3 atsmith3 added the enhancement New feature or request label May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant