riscv/rocket-chip
1
0
Fork 0
Code Releases Activity

Don't implicitly fence on CSR instructions

Browse Source 
CSRs that have an effect on I/O should use an explicit FENCE.
This commit is contained in:
Andrew Waterman 2016-10-01 19:39:36 -07:00
parent b772edcb1b
commit e0188f8aa4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/scala/rocket/rocket.scala
View File

@ -263,7 +263,7 @@ class Rocket(implicit p: Parameters) extends CoreModule()(p) {
mem_reg_valid && mem_ctrl.rocc || wb_reg_valid && wb_ctrl.rocc)
id_reg_fence := id_fence_next || id_reg_fence && id_mem_busy
val id_do_fence = id_rocc_busy && id_ctrl.fence ||
id_mem_busy && (id_ctrl.amo && id_amo_aq || id_ctrl.fence_i || id_reg_fence && (id_ctrl.mem || id_ctrl.rocc) || id_csr_en)
id_mem_busy && (id_ctrl.amo && id_amo_aq || id_ctrl.fence_i || id_reg_fence && (id_ctrl.mem || id_ctrl.rocc))
val bpu = Module(new BreakpointUnit(nBreakpoints))
bpu.io.status := csr.io.status