-
Notifications
You must be signed in to change notification settings - Fork 7
commits extracted from sysemu PR #103
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
base: tip
Are you sure you want to change the base?
Conversation
2888929
to
23deaa4
Compare
These commits were identified during review as being not strictly related to system emulation. |
Signed-off-by: Brian Cain <[email protected]>
The BADVA reg is referred to with the wrong identifier. The CAUSE reg field of SSR is not yet modeled, we will dump the SSR in a subsequent commit. Signed-off-by: Brian Cain <[email protected]>
Signed-off-by: Brian Cain <[email protected]>
To remove any confusion with HVX or other potential store instructions, we'll qualify this context var with "scalar". Signed-off-by: Brian Cain <[email protected]>
eaee221
to
b8e3210
Compare
It's odd to have |
As specified by the PRM, we should raise an exception when a packet contains multiple writes to the same register. Lets introduce a bitmap at the CPUArchState, looking for writes to already written registers and properly generate an exception when needed. Also add a test case to tests/tcg/system. The added test shows a scenario in which multiple writes are performed to the same register but qemu fails to detect that and throw the appropriated exception. This happens because we are not cleaning hex_slot_cancelled as frequently as we should, so an old state is used and the packet that should raise an exception is considered as cancelled by the code that would detect the multiple writes issue. Let's fix that by cleaning hex_slot_canceled on all conditional instructions instead, which should cover all cases where the variable is used to detect multiple writes. Signed-off-by: Matheus Tavares Bernardino <[email protected]>
We should raise an exception in the event that we encounter a packet that can't be correctly decoded, not fault. Signed-off-by: Brian Cain <[email protected]>
Signed-off-by: Brian Cain <[email protected]>
b8e3210
to
23b3879
Compare
squashed, thanks for the suggestion. |
No description provided.