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

Clarify multiple VA to PA mapping #7

Merged
merged 3 commits into from
Dec 2, 2024
Merged

Clarify multiple VA to PA mapping #7

merged 3 commits into from
Dec 2, 2024

Conversation

sqzsq
Copy link
Collaborator

@sqzsq sqzsq commented Nov 19, 2024

Added note on software's responsibility because tags are defined on VA.

@sqzsq sqzsq requested a review from deepak0414 November 19, 2024 08:33
src/mte_tag.adoc Outdated
@@ -218,6 +218,11 @@ splitted stores.
A memory access (load or store) to some virtual address `va` can not bypass
the older store initiated by `settag/setinvtag rs1=va`.

This specification defines tag as the entitiy attached to virtual addresses.
Copy link
Collaborator

Choose a reason for hiding this comment

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

s/entitiy attached/entity associated/

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed

src/mte_tag.adoc Outdated
This specification defines tag as the entitiy attached to virtual addresses.
It is software's responsibility to ensure that the tags are appropriately set
on the virtual addresses even though some of them map to the same physical
address(es).
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we re-word this

"""
It is software's responsibility to ensure that the tags are appropriately set
on the virtual addresses even though some of them map to the same physical
address(es)
"""

to something like

"""
In case of aliasing (multiple virtual addresses map to same physical address), it is software's
responsibility to ensure that the tags are set correctly for respective virtual address prior to
memory accesses via aliased virtual address.
"""

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Revised as suggested.

@deepak0414 deepak0414 merged commit 93ac731 into riscv:main Dec 2, 2024
2 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.

2 participants