RE: [PATCH] target/i386: Raise the highest index value used for any VMCS encoding

"Li, Xin3" <xin3.li@xxxxxxxxx> · Fri, 26 Jul 2024 01:12:42 +0000

> On Wed, Jul 24, 2024 at 10:09 AM Lei Wang <lei4.wang@xxxxxxxxx> wrote:
> > Because the index value of the VMCS field encoding of Secondary
> > VM-exit controls, 0x44, is larger than any existing index value, raise
> > the highest index value used for any VMCS encoding to 0x44.
> >
> > Because the index value of the VMCS field encoding of FRED
> > injected-event data (one of the newly added VMCS fields for FRED
> > transitions), 0x52, is larger than any existing index value, raise the
> > highest index value used for any VMCS encoding to 0x52.
> 
> Hi, can you put together a complete series that includes all that's needed for
> nested FRED support?
> 

We can do it.

Just to be clear, this patch is not needed to enable nested FRED, but to
fix the following vmx test in kvm-unit-tests, otherwise we get:
    FAIL: VMX_VMCS_ENUM.MAX_INDEX expected: 29, actual: 19

Thanks!
    Xin