Update description of ERR_INFO.etype = 0x2 for AMO transactions and fix inconsistency #40
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
* Add AMO (atomic memory operation) to Table 1. Glossary and Acronyms in chapter2.adoc. * Update some words about "illegal write access" to "illegal write access/AMO" in chapter2.adoc. * Add a note about an AMO transaction must be granted by checking read and write access permissions in chapter2.adoc. * Update description of ERR_INFO.etype = 0x2 in chapter5.adoc, it should be "illegal write access/AMO". * Update description of ERR_INFO.ttype = 0x2 in chapter5.adoc, it should be "write access/AMO". Signed-off-by: tyshyu <[email protected]>
Fix some inconsistency about illegal instruction fetch. Signed-off-by: tyshyu <[email protected]>
Signed-off-by: tyshyu <[email protected]>
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.
In V0.9.2-RC3,
ERR_INFO.etype= 0x2 is"illegal write access". However, to cover atomic memory operation (AMO) transactions,ERR_INFO.etype= 0x2 should be "illegal write access/AMO". It is likemcause"Store/AMO access fault" (0x7) in a RISC-V hart.The PR updates related words for
ERR_INFO.etype= 0x2.BTW, some inconsistencies about
ERR_INFO.etype= 0x3 are also fixed in the PR.The following list the updates:
ERR_INFO.etype= 0x2 in chapter5.adoc, it should be "illegal write access/AMO".ERR_INFO.ttype= 0x2 in chapter5.adoc, it should be "write access/AMO".ERR_INFO.etype= 0x3.