[PATCH] x86: drop vex_encoding_vex2 enumerator

[Jan Beulich]

On 17.01.2020 15:48, H.J. Lu wrote:
> On Fri, Jan 17, 2020 at 1:03 AM Jan Beulich <jbeulich@suse.com> wrote:
>>
>> On 16.01.2020 23:32,  H.J. Lu  wrote:
>>> How about this?
>>
>> For {vex2} "if possible" still leaves open what happens if this
>> is not possible. Aiui there are two distinct cases:
>> - 3-byte VEX could be used, in which case the prefix is ignored
> 
> Did you mean "must be used"?

Well, yes, in a way.

>> - only legacy or EVEX encoding is possible, in which case there'd
>>   be an error (not really sure about EVEX here)
>> I think it would be better to have {vex} and {vex3}.
> 
> Agreed.  I will make the change and keep {vex2} for backward compatibility.
> How about this patch?
> 
>> Furthermore both say "for VEX instruction", leaving open what is
>> to happen for non-VEX-encodable ones. It also leaves open what
>> their interaction with XOP-encoded insns is.
> 
> Here is the updated document.

Looks good, thanks.

Jan