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

Define AP field for Infinite on purecap and legacy exts #197

Merged
merged 5 commits into from
Apr 12, 2024

Conversation

andresag01
Copy link
Collaborator

The MXLEN=32 encoding for the AP field was recently changed. However, the following remained unclear:

  1. The encoding of the AP field for MXLEN=32 when Zcheri_legacy is or is not supported
  2. The encoding of the Infinite capability for MXLEN=32.

For (1), this change ensures that the AP encodings for Mode=Legacy are "reserved" in valid capabilities (ie. we cannot have a valid tag with an encoding that has Mode=Legacy).

For (2), the tables and text are updated such that the AP encoding for the Infinite Capability is:

  • 9 when Zcheri_purecap is supported but Zcheri_legacy is not
  • 8 when Zcheri_purecap and Zcheri_legacy are both supported

@andresag01
Copy link
Collaborator Author

@tariqkurd-repo : I resolved all your comments because we talked through them and I made changes as discussed. Could you take another look? Thanks!

@tariqkurd-repo tariqkurd-repo self-requested a review April 12, 2024 15:08
Copy link
Collaborator

@arichardson arichardson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments otherwise good to go.

andresag01 and others added 2 commits April 12, 2024 18:34
Co-authored-by: Alexander Richardson <[email protected]>
Signed-off-by: Andres Amaya Garcia <[email protected]>
@andresag01 andresag01 merged commit 7b27018 into riscv:main Apr 12, 2024
3 checks passed
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

Successfully merging this pull request may close these issues.

3 participants