On Fri, 2017-07-28 at 13:53 +0200, Paolo Bonzini wrote:
> On 28/07/2017 10:24, Mike Galbraith wrote:
> > On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote:
> >> With these two patches, KVM does not blindly pass the exit interruption
> >> info and exit qualification from the vmcs02 and vmcs12 w
On 28/07/2017 10:24, Mike Galbraith wrote:
> On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote:
>> With these two patches, KVM does not blindly pass the exit interruption
>> info and exit qualification from the vmcs02 and vmcs12 when injecting
>> an exception. There were two spots where this
2017-07-28 16:24 GMT+08:00 Mike Galbraith :
> On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote:
>> With these two patches, KVM does not blindly pass the exit interruption
>> info and exit qualification from the vmcs02 and vmcs12 when injecting
>> an exception. There were two spots where this
On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote:
> With these two patches, KVM does not blindly pass the exit interruption
> info and exit qualification from the vmcs02 and vmcs12 when injecting
> an exception. There were two spots where this was done, namely
> nested_vmx_check_exception an
With these two patches, KVM does not blindly pass the exit interruption
info and exit qualification from the vmcs02 and vmcs12 when injecting
an exception. There were two spots where this was done, namely
nested_vmx_check_exception and vmx_inject_page_fault_nested.
Patch 1 avoids writing the vmcs
5 matches
Mail list logo
