[PATCH] x86: drop vex_encoding_vex2 enumerator

[Jan Beulich]

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
- 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}.

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.

Jan