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

LSU: trigger accessfault for vector mmio access request #3168

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

weidingliu
Copy link
Member

@weidingliu weidingliu commented Jul 9, 2024

This commit is to ensure robustness when vector instructions are used to access MMIO regions by mistake. Currently, we do not support vector instruction access to MMIO regions, and in order to handle the situation when a vector instruction incorrectly accesses an MMIO region, an accessfault exception is triggered when the MMIO region is accessed using a vector instruction.

This commit is to ensure that errors are handled when vector instructions are used to access MMIO regions by mistake.
Currently, we do not support vector instruction access to MMIO regions, and in order to handle the situation when a vector instruction incorrectly accesses an MMIO region, an accessfault exception is triggered when the MMIO region is accessed using a vector instruction.
@XiangShanRobot
Copy link

[Generated by IPC robot]
commit: dc903e5

commit astar copy_and_run coremark gcc gromacs lbm linux mcf microbench milc namd povray wrf xalancbmk
dc903e5 1.784 0.458 2.003 1.199 2.920 2.498 2.207 0.928 1.374 1.441 3.153 2.600 2.385 2.956

master branch:

commit astar copy_and_run coremark gcc gromacs lbm linux mcf microbench milc namd povray wrf xalancbmk
dab1ad8 1.784 0.458 2.003 1.199 2.920 2.498 2.207 0.928 1.374 1.441 3.153 2.600 2.385 2.956
c6655c9 1.784 0.458 2.003 1.199 2.920 2.498 2.207 0.928 1.374 1.441 3.153 2.600 2.385 2.956
340ef6e 1.784 0.458 2.003 1.199 2.920 2.498 2.207 0.928 1.374 1.441 3.153 2.600 2.385 2.956
571677c 1.784 0.458 2.003 1.199 2.920 2.498 2.207 0.928 1.374 1.441 3.153 2.600 2.385 2.956
6bb8be2 1.784 0.458 2.003 1.199 2.920 2.498 2.197 0.927 1.374 1.441 3.153 2.600 2.385 2.956
854ed34 1.784 0.458 2.003 1.199 2.920 2.498 2.198 0.928 1.374 1.441 3.153 2.600 2.385 2.956
27d7dfe 1.784 0.458 2.003 1.199 2.920 2.498 2.197 0.928 1.374 1.441 3.153 2.600 2.385 2.956
9194610 1.784 0.458 2.003 1.199 2.920 2.498 2.197 0.928 1.374 1.441 3.153 2.600 2.385 2.956
1e2f098 1.784 0.458 2.003 1.199 2.920 2.498 2.197 0.928 1.374 1.441 3.153 2.600 2.385 2.956
828a8a4 1.784 0.458 2.003 1.199 2.920 2.498 2.197 0.928 1.374 1.441 3.153 2.600 2.385 2.956

@Tang-Haojin Tang-Haojin merged commit 11d5798 into OpenXiangShan:master Jul 11, 2024
7 checks passed
@weidingliu weidingliu deleted the vlsu-patch branch July 12, 2024 10:23
sinceforYy pushed a commit to sinceforYy/XiangShan that referenced this pull request Jul 16, 2024
…n#3168)

This commit is to ensure robustness when vector instructions are used to
access MMIO regions by mistake. Currently, we do not support vector
instruction access to MMIO regions, and in order to handle the situation
when a vector instruction incorrectly accesses an MMIO region, an
accessfault exception is triggered when the MMIO region is accessed
using a vector instruction.
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.

4 participants