From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: add back pending timer irqs for kernel APIC timer Date: Mon, 13 Aug 2007 16:36:43 +0300 Message-ID: <46C05E6B.3080101@qumranet.com> References: <10EA09EFD8728347A513008B6B0DA77A01E8DA94@pdsmsx411.ccr.corp.intel.com> <46BC9A7E.5040206@qumranet.com> <10EA09EFD8728347A513008B6B0DA77A01E8DACC@pdsmsx411.ccr.corp.intel.com> <46C01B58.8080402@qumranet.com> <1187006514.4165.1.camel@ghaskins-t60p.haskins.net> <10EA09EFD8728347A513008B6B0DA77A014E8AD1@pdsmsx411.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: "Dong, Eddie" Return-path: In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A014E8AD1-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Dong, Eddie wrote: >> 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. > Why is this important? An hrtimer is just an entry on a list, no? Do you mean, just if the guest is preempted (not during hlt)? Is it so important? We're talking a few thousand wakeups per second. > 3: Use scale + shift like Xen did to make sure no internal overflow if > we run guest contiguously for long time say 2 years. > hrtimers are in 64-bit nanoseconds. That gives about 160 years. > Above 1-3 is already in Xen and we just need to port. > > > 4: Should we use hrtimer? How efficieny it is? > > > Sure, hrtimer is the future. > Will u be able to help together? > thx,eddie > -- 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/