Re: Re: [PATCH v8 12/20] KVM: x86: Support REX2-prefixed opcode decode

From: Christian Ludloff

Date: Wed Nov 18 2026 - 07:43:11 EST


>> Does hardware raise #UD on 0x48 0x66 0xD5, or does the intervening legacy
>> prefix nullify the REX prefix as in legacy encodings?
>
> Yes, it is nullified and this behavior should be preserved, I think. I
> was also able to verify this on an APX-prototyped system.
>
>> The text clearly permits 0x48 0x66 0xD5, since the REX prefix doesn't
>> *immediately* precede the REX2 prefix. The table is unclear.
>
> I'll pass this documentation feedback along to the relevant folks.

Fwiw, EVO processors have MSR control bits for this –
#UD vs not, REX/REX2 bits merged vs not, plus more.

--
C.