> > > Note that my old lapic branch did a similar "tdf" thing as well and it > worked quite nicely, so I think Eddie is on the right track with > adding this.
I just copied the whole APIC timer stuff from your old patch at that time as TODO. maybe I missed something :-( Time virtualization has quit a long way to go and it is quit very beginning now. Something in my plan: 1: Current 3 patches to fix the pending irq issues and accumulate issue. 2: stop hrtimer when the guest is descheduled to increase scalibility and remove apic->lock. 3: Use scale + shift like Xen did to make sure no internal overflow if we run guest contiguously for long time say 2 years. Above 1-3 is already in Xen and we just need to port. 4: Should we use hrtimer? How efficieny it is? Will u be able to help together? thx,eddie ------------------------------------------------------------------------- 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
