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

Sscofpmf editorial fixes. #1316

Merged
merged 4 commits into from
Apr 4, 2024
Merged

Sscofpmf editorial fixes. #1316

merged 4 commits into from
Apr 4, 2024

Conversation

wmat
Copy link
Collaborator

@wmat wmat commented Apr 3, 2024

For the beginning of the descriptions of bits 58 and 59, "If set, ..." should instead be "If set and the H extension is implemented, ...".

In the last paragraph, "In M and S modes, ..." should instead say "In S mode, ...".

For the beginning of the descriptions of bits 58 and 59, "If set, ..." should instead be "If set and the H extension is implemented, ...".

In the last paragraph, "In M and S modes, ..." should instead say "In S mode, ...".
@wmat wmat requested a review from gfavor April 3, 2024 16:26
src/sscofpmf.adoc Outdated Show resolved Hide resolved
@@ -183,7 +183,7 @@ M-mode).

Read access to bit _X_ is subject to the same mcounteren (or mcounteren and
hcounteren) CSRs that mediate access to the hpmcounter CSRs by S-mode (or
VS-mode). In M and S modes, scountovf bit _X_ is readable when mcounteren bit
VS-mode). In S modes, scountovf bit _X_ is readable when mcounteren bit
Copy link
Member

Choose a reason for hiding this comment

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

@gfavor Don't we need to say what happens in M-mode, e.g. add a sentence before this one like "In M-mode, scountovf bit X is always readable."

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yes re scountovf. @wmat , the overall change should be replacing the "In M and S modes, ..." sentence with the following two sentences:

In M mode, scountovf bit X is always readable. In S/HS modes, scountovf bit X is readable when mcounteren bit X is set, and otherwise reads as zero.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've made the change as described, however, is S/HS correct? Should it be S/VS?

Suggested change
VS-mode). In S modes, scountovf bit _X_ is readable when mcounteren bit
VS-mode). In M mode, scountovf bit X is always readable, in S/HS modes, scountovf bit _X_ is readable when mcounteren bit

Copy link
Collaborator

@gfavor gfavor left a comment

Choose a reason for hiding this comment

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

Assuming Bill makes the updated change, I'm good overall with this PR.

Copy link
Member

@aswaterman aswaterman left a comment

Choose a reason for hiding this comment

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

👍 I'll make a final review before merging.

wmat added 2 commits April 4, 2024 10:23
Reworded Bits 58 & 59 description to "If set, then counting of events in VU-mode is inhibited. But if the H extension is
 implemented, then this bit is read-only-zero."
Updated the text for scountovf.
src/sscofpmf.adoc Outdated Show resolved Hide resolved
@aswaterman aswaterman merged commit cdff4e7 into main Apr 4, 2024
2 checks passed
@aswaterman aswaterman deleted the Sscofpmf-editorial-fixes branch April 4, 2024 21:28
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