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

HART specific opearations at DRAM controller / adding hartid to memory requests #3632

Open
FelixWagner00 opened this issue May 19, 2024 · 0 comments

Comments

@FelixWagner00
Copy link

FelixWagner00 commented May 19, 2024

Type of issue: other enhancement

Impact: make memory requests separetable by HART at the external memory level

I am currently looking into expanding the memory request operation with the information of which HART is sending it.
The L1d$ accepts memory requests from the rocket core and checks if it is cached. If uncached it sends an acquire message over the TileLink network to the L2$ or directly to the external memory (dependent if L2 cache is to be included or not).
At this point the L2$ only receives an ACQUIRE operation over TileLink which carries Source, Address, Size and a Permission operation.

How exactly is the Source and Address determined?

Is it possible to include the hartid in this acquire message or is it necessary to implement a custom acquire message.
Or is routing the hartid outside of the TileLink network using wires between the components my only option?

Many thanks.

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

1 participant