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

"the address being access and which caused the trigger to fire" #1102

Open
tariqkurd-repo opened this issue Jan 24, 2025 · 0 comments
Open

Comments

@tariqkurd-repo
Copy link

tariqkurd-repo commented Jan 24, 2025

Image

From this text where, for example, an LW loads bytes 0x4000, 0x4001, 0x4002, 0x4003
A watchpoint fires at address 0x4001
What is the reported VA value?

Is the address being accessed 0x4000? i.e. the calculated VA, and as a result the watchpoint fired.
Or does it mean the actual byte address needs to be reported i.e. 0x4001.

If it does mean the actual byte address, then it would help to clarify the wording.

it also doesn't say which address to return in the case of a NAPOT match where multiple can hit

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

No branches or pull requests

1 participant