Dong, Eddie wrote: > Avi Kivity wrote: > >> Dong, Eddie wrote: >> >>> Avi: >>> After one more thinking, I found something others. >>> kvm_vcpu_ioctl_get_sregs/kvm_vcpu_ioctl_set_sregs doesn't save >>> current injecting exception while Xen does. Which includes >>> VM_ENTRY_INTR_INFO & VM_ENTRY_EXCEPTION_ERROR_CODE. Any special >>> reason? >>> >>> >> No special reason, never saw the need for it. >> >> Do you see exits with this set? It's probably better to loop again >> instead of saving it, because this is an implementation detail rather >> than real state (e.g. state that qemu has as well). >> >> > In SMP case, we don't know what status a VCPU is in. They are actually > same with IDT_Vectoring. > Current master only push back external irqs, actually an exception may > also cause injection failure. > It is difficult to wait for all VCPUs to get those info handed fully. UP > may be OK. > >
I think that no sane OS gets exceptions on interrupts? -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
