From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52460 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OF9YH-0000Tc-4A for qemu-devel@nongnu.org; Thu, 20 May 2010 13:28:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OF9YF-0006pc-DW for qemu-devel@nongnu.org; Thu, 20 May 2010 13:28:57 -0400 Received: from kelvin.asmallorange.com ([207.210.111.10]:41115) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OF9YF-0006fw-8E for qemu-devel@nongnu.org; Thu, 20 May 2010 13:28:55 -0400 Date: Thu, 20 May 2010 22:57:42 +0530 From: Rabin Vincent Message-ID: <20100520172741.GA28134@debian> References: <1272793852-26260-1-git-send-email-rabin@rab.in> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1272793852-26260-1-git-send-email-rabin@rab.in> Subject: [Qemu-devel] Re: [PATCH 1/2] arm_timer: reload timer when enabled List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: paul@codesourcery.com On Sun, May 02, 2010 at 03:20:51PM +0530, Rabin Vincent wrote: > Reload the timer when TimerControl is written, if the timer is to be > enabled. Otherwise, if an earlier write to TimerLoad was done while > periodic mode was not set, s->delta may incorrectly still have the value > of the maximum limit instead of the value written to TimerLoad. > > This problem is evident on versatileap on current linux-next, which > enables TIMER_CTRL_32BIT before writing to TimerLoad and then enabling > periodic mode and starting the timer. This causes the first periodic > tick to be scheduled to occur after 0xffffffff periods, leading to a > perceived hang while the kernel waits for the first timer tick. > > Signed-off-by: Rabin Vincent Could these patches please be applied? What was then linux-next is now current Linux mainline, and it doesn't boot without this patch. Rabin