提交 4c3daa52 编写于 作者: Z ZhangZifei

param: set EnableUncacheWriteOutstanding to false

Here is a bug cause by EnableUncacheWriteOutstanding:
The case is extintr in Nexus-AM.
Three steps of the test:
  clear intrGen's intr: Stop pass interrupt. A mmio write.
  clear plic claim: complete intr. A mmio write.
  read plic claim to check: claim should be 0. A mmio read.
The corner case:
  intrGen's mmio write is to slow. The instruction after it executes
and plic claim's mmio's write & read execute before it. On the side of
core with plic, claim is cleared. But on the side of intrGen with plic,
the source of interrupt is still enabled and trigger interrupt.
So the "read plic claim to check" get a valid claim and failed.
上级 5549d5de
......@@ -175,7 +175,7 @@ case class XSCoreParameters
EnableCacheErrorAfterReset: Boolean = true,
EnableDCacheWPU: Boolean = false,
EnableAccurateLoadError: Boolean = true,
EnableUncacheWriteOutstanding: Boolean = true,
EnableUncacheWriteOutstanding: Boolean = false,
MMUAsidLen: Int = 16, // max is 16, 0 is not supported now
ReSelectLen: Int = 6, // load replay queue replay select counter len
itlbParameters: TLBParameters = TLBParameters(
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册