Re: [PATCH] x86/HVM: tidy state on hvmemul_map_linear_addr()'s error path

On 08.02.2024 17:11, Paul Durrant wrote: > On 08/02/2024 15:59, Jan Beulich wrote: >> On 06.02.2024 13:06, Jan Beulich wrote: >>> While in the vast majority of cases failure of the function will not >>> be followed by re-invocation with the same emulation context, a few >>> very specific insns -

Re: [PATCH] x86/HVM: tidy state on hvmemul_map_linear_addr()'s error path

On 08/02/2024 15:59, Jan Beulich wrote: On 06.02.2024 13:06, Jan Beulich wrote: While in the vast majority of cases failure of the function will not be followed by re-invocation with the same emulation context, a few very specific insns - involving multiple independent writes, e.g. ENTER and

Re: [PATCH] x86/HVM: tidy state on hvmemul_map_linear_addr()'s error path

On 06.02.2024 13:06, Jan Beulich wrote: > While in the vast majority of cases failure of the function will not > be followed by re-invocation with the same emulation context, a few > very specific insns - involving multiple independent writes, e.g. ENTER > and PUSHA - exist where this can happen.

[PATCH] x86/HVM: tidy state on hvmemul_map_linear_addr()'s error path

While in the vast majority of cases failure of the function will not be followed by re-invocation with the same emulation context, a few very specific insns - involving multiple independent writes, e.g. ENTER and PUSHA - exist where this can happen. Since failure of the function only signals to