From b03e3c5b1a43ced11df6baf00a931d47e2e30159 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Sun, 29 Apr 2018 16:09:35 +0100 Subject: [PATCH] clarify --- isa_conflict_resolution.mdwn | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index 6d11681eb..5538a7add 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -347,7 +347,9 @@ Update 29apr2018: mvendorid-marchid setting is incapable of correctly interpreting. To fix this it will be necessary for implementations (hardware / software) to set up separate per-mvendorid-marchid trap handlers and - for the hardware (or software) to switch to the appropriate trap "set". + for the hardware (or software) to switch to the appropriate trap "set" + when the mvendorid-marchid is written to. The switch to a different + "set" will almost undoubtedly require (transparent) hardware assistance. * It's been noted that there may be certain legitimate cases where an mvendorid-marchid should *specifically* not be tested for RISC-V Certification Compliance: native support for foreign architectures -- 2.30.2