From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37620) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SfOlm-0002yu-98 for qemu-devel@nongnu.org; Fri, 15 Jun 2012 01:08:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SfOlk-0005KW-7C for qemu-devel@nongnu.org; Fri, 15 Jun 2012 01:08:25 -0400 Received: from lemon.ertos.nicta.com.au ([203.143.174.143]:59765 helo=lemon.ken.nicta.com.au) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SfOlj-0005KD-SC for qemu-devel@nongnu.org; Fri, 15 Jun 2012 01:08:24 -0400 Date: Fri, 15 Jun 2012 15:07:55 +1000 Message-ID: From: Peter Chubb In-Reply-To: References: <4FD9ACBC.2090304@redhat.com> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: Re: [Qemu-devel] Broken Microblaze timer List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: Anthony Liguori , "qemu-devel@nongnu.org Developers" , Peter Chubb , Paul Brook , Paolo Bonzini , "Edgar E. Iglesias" >>>>> "Peter" == Peter Crosthwaite writes: Peter> So ptimer has safeguards against misuse in periodic mode but Peter> not one-shot mode? This strikes me as inconsistent. I.E. for Peter> one use case the safeguard is in ptimer, and the other in the Peter> client device. I think if we are in the bussiness of putting Peter> these safeguards in ptimer itself then it should be there for Peter> all use cases yes? I.E. the fix for this is making sure Peter> one-shot ptimer give the cpu a look in. When a one-shot timer fires, it has to be reset by the CPU before it'll fire again. So the CPU always gets a look in --- or ought to. -- Dr Peter Chubb peter.chubb AT nicta.com.au http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA