>>> On 10.12.18 at 15:26, wrote:
> On 10/12/2018 14:11, Jan Beulich wrote:
> On 10.12.18 at 14:50, wrote:
>>> On 07/12/2018 11:17, Jan Beulich wrote:
The check needs to happen whenever EVEX.b is clear, not just in the
memory operand case.
>>> EVEX.b is a different field to EVEX.br
On 10/12/2018 14:11, Jan Beulich wrote:
On 10.12.18 at 14:50, wrote:
>> On 07/12/2018 11:17, Jan Beulich wrote:
>>> The check needs to happen whenever EVEX.b is clear, not just in the
>>> memory operand case.
>> EVEX.b is a different field to EVEX.br
>>
>> I'm afraid that this goes back to
>>> On 10.12.18 at 14:50, wrote:
> On 07/12/2018 11:17, Jan Beulich wrote:
>> The check needs to happen whenever EVEX.b is clear, not just in the
>> memory operand case.
>
> EVEX.b is a different field to EVEX.br
>
> I'm afraid that this goes back to my original concern with the series.
>
On 07/12/2018 11:17, Jan Beulich wrote:
> The check needs to happen whenever EVEX.b is clear, not just in the
> memory operand case.
EVEX.b is a different field to EVEX.br
I'm afraid that this goes back to my original concern with the series.
Having the fields named differently between our code
The check needs to happen whenever EVEX.b is clear, not just in the
memory operand case.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/x86_emulate/x86_emulate.c
+++ b/xen/arch/x86/x86_emulate/x86_emulate.c
@@ -8526,11 +8526,9 @@ x86_emulate(
case X86EMUL_OPC_EVEX_66(0x0f38, 0xbd): /*
