Avi Kivity wrote: > Zhang, Xiantao wrote: [in struct kvm_vcpu] >> int interrupt_window_open; > arch specific, though maybe it's close enough to generic
I thought about this field for a while. What we really want, is that the common code can figure wheter or not it is a good idea to send an interrupt. All architectures (even including s390) could encode an interrupt number in a 64bit value. To me, it looks like a callback for this like int kvm_arch_interrupt_window_open(u64 interrupt); would be the right abstraction. No need to solve this whole thing with this patch though, that aims at splitting kvm_vcpu. so long, Carsten ------------------------------------------------------------------------- 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
