Dor Laor wrote:
>>>> Are you sure? the kvm_vmx_exit_handlers function pointer arrays has
>>>> the index named EXIT_REASON_EXCEPTION_NMI, so it must be handled as
>>>> NMI to me.
>>>>         
>>> This exit reason is either NMI, or software interrupt or exception.
>>>
>>> Refer update_exception_bitmap for the setting of VM Exit for which
>>> exception (int n).
>>>
>>> In normal situation, I think guest int 1/3 directly get handled in
>>> guest.
>>>       
>> So you mean interrupts 1/3 do not cause VMExit??
>>     
>
> Int 1 is updated in the update_exception_bitmap, so it does causes
> vmexit.
>   

This only happens if guest debugging is enabled (i.e. the host is 
debugging the guest).  However, if the guest is debugging itself, then 
these exceptions shouldn't be trapped.  Note that guest debugging and 
guest self debugging cannot be supported simultaneously using hardware 
debug support.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to