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

Triggering an interrupt may not record the error information #24

Open
leBsky opened this issue Nov 21, 2024 · 1 comment
Open

Triggering an interrupt may not record the error information #24

leBsky opened this issue Nov 21, 2024 · 1 comment

Comments

@leBsky
Copy link

leBsky commented Nov 21, 2024

The spec claims that "The error capture record maintains the specifics of the first illegal access detected, except if the
following two conditions are held: (1) any interrupt-suppress bit regarding the access is set, and (2) no
bus error is returned" I understand that it means error record requires no interrupt suppression and no bus error suppression.

In this case, when an interrupt is not suppressed but bus error is suppressed, the interrupt will be triggered and it should update ERR_REQINFO.v to 1 to denote the interrupt pending status. However, from the perspective of error recording mechanism, since the bus error suppression is detected, then it will not update the ERR_REQINFO.v. Please help clarify the inconsistent condition.

@tyshyu
Copy link
Contributor

tyshyu commented Nov 25, 2024

In this case, the error record (ERR_REQINFO.v also is a part of error record) will be updated because condition (1) is not held.

Error record will not be updated when conditions both are held (interrupt is suppressed and bus error is suppressed).

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

2 participants