>On 6/25/07, Dong, Eddie <[EMAIL PROTECTED]> wrote: >> [EMAIL PROTECTED] wrote: >> > On 6/25/07, Dor Laor <[EMAIL PROTECTED]> wrote: >> >>> I am wondering how KVM handles debug and breakpoint interrupt? Does >> >>> it process them like normal NMI interrupt, or is there any special >> >>> processing? >> >>> >> >> >> >> I haven't use it but KVM does support qemu'd gdbstub. Both single >> >> step and breakpoint are possible. From the source code (vmx.c) it >> >> seems like handle_exception function handle them as regular >> >> exceptions (non nmi). >> > >> > 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. >Thanks, >Jun ------------------------------------------------------------------------- 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
