Thanks Paolo! That makes sense, KVM has to inject the #UD in order for
the guest to deliver the exception in the guest user space.
On Wed, May 7, 2014 at 1:55 AM, Paolo Bonzini wrote:
> Il 06/05/2014 22:11, Alexandru Duţu ha scritto:
>
>> What is puzzling thought is the fact that e
ces
a KVM exit if the instruction is not emulated by KVM and it re-enters
virtualized execution if the instruction is emulated?
Best,
Alex
On Tue, May 6, 2014 at 11:56 AM, Paolo Bonzini wrote:
> Il 05/05/2014 17:56, Alexandru Duţu ha scritto:
>
>>
>> It seems that re-entering virt
kernel module?
Best regards,
Alex
On Mon, May 5, 2014 at 7:07 PM, Nakajima, Jun wrote:
> On Mon, May 5, 2014 at 11:48 AM, Alexandru Duţu wrote:
>> Thank you Jun! I see that in case of VMX does not emulated the
>> instruction that produced a UD exception, it just queues the e
that KVM, in case of VMX, will exit
immediately on UD.
I am not sure what you meant with MOVBE emulation.
Thanks,
Alex
On Mon, May 5, 2014 at 12:34 PM, Nakajima, Jun wrote:
> On Mon, May 5, 2014 at 8:56 AM, Alexandru Duţu wrote:
>> Dear all,
>>
>> It seems that currentl
Dear all,
It seems that currently, on UD interception KVM does not exit
completely. Virtualized execution finishes, KVM executes
ud_intercept() after which it enters virtualized execution again.
I am working on accelerating with virtualized execution a simulator
that emulates system calls. Essent
