On 07.03.2017 15:35, Alex Bennée wrote:
>
> Paolo Bonzini writes:
>
>> Paths through the softmmu code during code generation now need to be audited
>> to check for double locking of tb_lock. In particular, VMEXIT can take
>> tb_lock
>> through cpu_vmexit -> cpu_x86_update_cr4 -> tlb_flush.
>>
Paolo Bonzini writes:
> Paths through the softmmu code during code generation now need to be audited
> to check for double locking of tb_lock. In particular, VMEXIT can take
> tb_lock
> through cpu_vmexit -> cpu_x86_update_cr4 -> tlb_flush.
>
> To avoid this, split VMEXIT delivery in two parts
Paths through the softmmu code during code generation now need to be audited
to check for double locking of tb_lock. In particular, VMEXIT can take tb_lock
through cpu_vmexit -> cpu_x86_update_cr4 -> tlb_flush.
To avoid this, split VMEXIT delivery in two parts, similar to what is done with
except
