Add GPU project chipyard changes

[richardyrh]

• Added Virgo/Radiance configs, memory coalescer configs, as well as a firesim config
• Added the radiance submodule
• Bumped rocket-chip, testchipip and gemmini with new commits
• Minor sbt and Makefile build system additions

Related PRs / Issues:

Type of change:

• Bug fix
• New feature
• Other enhancement

Impact:

• RTL change
• Software change (RISC-V software)
• Build system change
• Other

Contributor Checklist:

• Did you set main as the base branch?
• Is this PR's title suitable for inclusion in the changelog and have you added a changelog:<topic> label?
• Did you state the type-of-change/impact?
• Did you delete any extraneous prints/debugging code?
• Did you mark the PR with a changelog: label?
• (If applicable) Did you update the conda .conda-lock.yml file if you updated the conda requirements file?
• (If applicable) Did you add documentation for the feature?
• (If applicable) Did you add a test demonstrating the PR?

• (If applicable) Did you mark the PR as Please Backport?

CI Help:
Add the following labels to modify the CI for a set of features.
Generally, a label added only affect subsequent changes to the PR (i.e. new commits, force pushing, closing/reopening).
See ci:* for full list of labels:

• ci:fpga-deploy - Run FPGA-based E2E testing
• ci:local-fpga-buildbitstream-deploy - Build local FPGA bitstreams for platforms that are released
• ci:disable - Disable CI

[richardyrh]

Requires chipsalliance/rocket-chip#3714, ucb-bar/gemmini#380

[jerryz123]

What is the use case for run-binaries-debug-bg? It just runs them in the background? Can't you just do make run-binaries .... & to do that?

Also, what is the change to riscv-tools-feedstock for?

[richardyrh]

What is the use case for run-binaries-debug-bg? It just runs them in the background? Can't you just do make run-binaries .... & to do that?

@hansungk's changes

Also, what is the change to riscv-tools-feedstock for?

Didn't mean to change that, will revert

[hansungk]

run-binaries-debug-bg makes sure the compile stage before sim is serialized. Was mostly for personal use though, we can leave it out

[jerryz123]

run-binaries-debug-bg makes sure the compile stage before sim is serialized. Was mostly for personal use though, we can leave it out

Hmm, the Makefile dependencies should already be enforcing compile ahead of sim... unless there's something which the Makefile isn't aware of that is a dependency.

[hansungk]

Yep, it's just that if you kick off many run-binaries-debug &, they might compile the same thing concurrently and might mangle some states. was mostly used for same config but different binary launches

[jerryz123]

I think there's a cleaner way to do this. What if you have the generator emit a supplementary file .custom.mems.conf via addResource in rocket-chip? Then in this make job, concatenate that file into TOP_SMEMS_CONF if it exists.

I don't like having this magic file in the vlsi/ directory.