Current value and location
Svadu.yaml currently lists Svade as a conflicting extension.

Expected value
Svadu and Svade should be able to co-exist:

• There is no mention in the spec of the extensions being incompatible with each other.
• The RVA23 profile requires Svade and has Svadu as an optional, additional extension. This isn't possible if they conflict with each other.
• The existing profiles & bases & extensions spreadsheet does not list them as conflicting extensions
• From the Linux kernel device tree documentation:

  Both Svade and Svadu extensions control the hardware behavior when the PTE A/D bits need to be set. The default behavior for the four possible combinations of these extensions in the device tree are:

  1. Neither Svade nor Svadu present in DT => It is technically unknown whether the platform uses Svade or Svadu. Supervisor software should be prepared to handle either hardware updating of the PTE A/D bits or page faults when they need updated.
  2. Only Svade present in DT => Supervisor must assume Svade to be always enabled.
  3. Only Svadu present in DT => Supervisor must assume Svadu to be always enabled.
  4. Both Svade and Svadu present in DT => Supervisor must assume Svadu turned-off at boot time. To use Svadu, supervisor must explicitly enable it using the SBI FWFT extension.