Uop queue #31
Open
Uop queue #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The full documentation for the uop queue design is here: https://github.com/Purdue-SoCET/RISCVBusiness/blob/rvv-f23/doc/src/rv32v/rv32v_uop_queue.md
Currently the vector decode block and the arbitration between scalar instructions and vector instructions are not supported yet. Only a scalar decode block is added.
The files for the uop queue are in the stage3/source directory and are the following:
The hazard unit also was modified to handle stalls, flushes, and exception pc handling due to the added uop stage.
The default queue length (maximum number of instructions the queue holds) is 8.
The default dispatch size (maximum number of instructions decoded in 1 cycle) is 1.
The uop_t data type of instructions inside the queue is defined in stage3/source/stage3_types_pkg.sv
Also in the verification folder under the pma-tests, pmp-tests, interrupts-exceptions tests, etc. I have added a build_and_run_all.py file to automate the build and testing procedure.