W dniu 18.12.2023 o 12:32, Peter Maydell pisze:
Enable FEAT_NV on the 'max' CPU, and stop filtering it out for the
Neoverse N2 and Neoverse V1 CPUs. We continue to downgrade FEAT_NV2
support to FEAT_NV for the latter two CPU types.
According to Neoverse-V1 TRM r1p2 it has FEAT_NV2. Similar with Neoverse-N2.
You wrote already:
in practice hypervisors such as KVM are going to require FEAT_NV2
and not bother to support the FEAT_NV-only case, so I have
implemented them one after the other in this single patchset.
So maybe they both should be FEAT_NV2 and FEAT_NV will be left unused.
Or enable FEAT_NV for V1 (as being older) and FEAT_NV2 on N2.
This way if someone wants to test nested virtualization then both
versions will be available without use of 'max' cpu.
