>>> On 11.10.17 at 18:52, wrote:
> On 10/11/2017 10:31 AM, Jan Beulich wrote:
> On 10.10.17 at 18:20, wrote:
>>> --- a/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
>>> +++ b/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
>>> @@ -40,6 +40,8 @@ struct fuzz_state
>>> uint64_t msr[MSR_IN
On 10/11/2017 10:31 AM, Jan Beulich wrote:
On 10.10.17 at 18:20, wrote:
>> --- a/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
>> +++ b/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
>> @@ -40,6 +40,8 @@ struct fuzz_state
>> uint64_t msr[MSR_INDEX_MAX];
>> struct segment_register
>>> On 10.10.17 at 18:20, wrote:
> --- a/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
> +++ b/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
> @@ -40,6 +40,8 @@ struct fuzz_state
> uint64_t msr[MSR_INDEX_MAX];
> struct segment_register segments[SEG_NUM];
> struct cpu_user_regs r
x86_emulate() operates not only on state passed to it in
cpu_user_regs, but also on state currently found on the cpu: namely,
the FPU and XMM registers. At the moment, we re-zero (and/or
re-initialize) cpu_user_regs on every invocation, but leave the
cpu-stored state alone. In "persistent mode",
