On Wed, May 22, 2019 at 2:13 AM Hesham Almatary
wrote:
>
> The current implementation unnecessarily checks for PMP even if MMU
> translation
> failed. This may trigger a wrong PMP access exception instead of
> a page exception.
>
> For example, the very first instruction fetched after the first s
The current implementation unnecessarily checks for PMP even if MMU translation
failed. This may trigger a wrong PMP access exception instead of
a page exception.
For example, the very first instruction fetched after the first satp write in
S-Mode will trigger a PMP access fault instead of an inst
On Tue, May 21, 2019 at 3:44 AM Hesham Almatary
wrote:
>
> The current implementation unnecessarily checks for PMP even if MMU
> translation
> failed. This may trigger a wrong PMP access exception instead of
> a page exception.
>
> For example, the very first instruction fetched after the first s
The current implementation unnecessarily checks for PMP even if MMU translation
failed. This may trigger a wrong PMP access exception instead of
a page exception.
For example, the very first instruction fetched after the first satp write in
S-Mode will trigger a PMP access fault instead of an inst