From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <18199.63230.583536.307945@cargo.ozlabs.ibm.com> Date: Fri, 19 Oct 2007 10:14:54 +1000 From: Paul Mackerras To: Sergei Shtylyov Subject: Re: [PATCH v2 3/4] Implement clockevents driver for powerpc In-Reply-To: <47177229.2030200@ru.mvista.com> References: <20070921032603.0D3EA32C887@thor> <4713A616.3090103@ru.mvista.com> <18195.64334.985238.848522@cargo.ozlabs.ibm.com> <47161D79.6000003@ru.mvista.com> <18198.43687.44059.477047@cargo.ozlabs.ibm.com> <47177229.2030200@ru.mvista.com> Cc: linuxppc-dev@ozlabs.org, Thomas Gleixner , Realtime Kernel List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sergei Shtylyov writes: > > What problem do you see arising from this? > > Timers firing too early. Only if the minimum interrupt latency is less than 1 decrementer tick. That seems pretty unlikely to me unless you have a very slow timebase frequency. In fact what we should program the decrementer to is: timeout - (is_booke? 0: 1) - min_interrupt_latency I was assuming that min_interrupt_latency (measured in timebase ticks) would be at least 1, but apparently some systems can have a timebase frequency as low as 1kHz, so we'll have to have an ifdef or something. Paul.