[EMAIL PROTECTED] wrote: > Avi, > > A couple of months back, we had a discussion about PMU virtualization > and the difficulty I encountered trying to catch the PMU interrupt > vector in kvm on VM-exit. KVM does not set ack_intr_on_intr. Would > you mind reminding me of the reason for this? > > On the topic of scheduler hooks for use by KVM, I think this > would help me also because it means I would not have to save > and restore the PMU registers on all VM-exit/VM-entry. At least
W/o the hook, the PMU save/restore can be done in heavy weight VM Exit path, the majority of VM Exit are light weight which doesn't need to do if you don't care the cycles spent in KVM. refer vmx_vcpu_put & vmx_vcpu_load. With hook, then we can further reduce the save/restore effort :-) ------------------------------------------------------------------------- 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
