target/riscv: Fix pmp NA4 implementation
The end address calculation for NA4 mode is wrong because the address used isn't shifted. It doesn't watch 4 bytes but a huge range because the end address calculation is wrong. The solution is to use the shifted address calculated for start address variable. Modifications are tested on Zephyr OS userspace test suite which works for other RISC-V boards (E31 and E34 core). Signed-off-by: Alexandre Mergnat <amergnat@baylibre.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Message-id: 20200706084550.24117-1-amergnat@baylibre.com Message-Id: <20200706084550.24117-1-amergnat@baylibre.com> [ Changes by AF: - Improve the commit title and message ] Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
This commit is contained in:
parent
895bfa84fe
commit
cfad709bce
@ -171,7 +171,7 @@ static void pmp_update_rule(CPURISCVState *env, uint32_t pmp_index)
|
||||
|
||||
case PMP_AMATCH_NA4:
|
||||
sa = this_addr << 2; /* shift up from [xx:0] to [xx+2:2] */
|
||||
ea = (this_addr + 4u) - 1u;
|
||||
ea = (sa + 4u) - 1u;
|
||||
break;
|
||||
|
||||
case PMP_AMATCH_NAPOT:
|
||||
|
Loading…
Reference in New Issue
Block a user