Re: [PATCH 5/6] vVMX: operand size in decode_vmx_inst()

2025-06-11 Thread Jan Beulich
On 11.06.2025 13:32, Andrew Cooper wrote: > On 11/06/2025 11:44 am, Jan Beulich wrote: >> Address size is entirely irrelevant to operand size determination; For >> VMREAD and VMWRITE outside of 64-bit mode operand size is 32 bits, while >> in 64-bit mode it's (naturally) 64 bits. For all other insn

Re: [PATCH 5/6] vVMX: operand size in decode_vmx_inst()

2025-06-11 Thread Andrew Cooper
On 11/06/2025 11:44 am, Jan Beulich wrote: > Address size is entirely irrelevant to operand size determination; For > VMREAD and VMWRITE outside of 64-bit mode operand size is 32 bits, while > in 64-bit mode it's (naturally) 64 bits. For all other insns it's 64 > bits (a physical address) or 128 bi

[PATCH 5/6] vVMX: operand size in decode_vmx_inst()

2025-06-11 Thread Jan Beulich
Address size is entirely irrelevant to operand size determination; For VMREAD and VMWRITE outside of 64-bit mode operand size is 32 bits, while in 64-bit mode it's (naturally) 64 bits. For all other insns it's 64 bits (a physical address) or 128 bits (INVEPT, INVVPID). To limit the amount of change