Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751272AbaDXEn6 (ORCPT ); Thu, 24 Apr 2014 00:43:58 -0400 Received: from mail-ob0-f175.google.com ([209.85.214.175]:43399 "EHLO mail-ob0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750703AbaDXEn4 (ORCPT ); Thu, 24 Apr 2014 00:43:56 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 24 Apr 2014 10:13:56 +0530 Message-ID: Subject: Re: [Query]: hrtimers: why don't we consider hrtimers in get_next_timer_interrupt() From: Viresh Kumar To: Preeti Murthy Cc: Thomas Gleixner , =?UTF-8?B?RnLDqWTDqXJpYyBXZWlzYmVja2Vy?= , Lists linaro-kernel , Linux Kernel Mailing List , Linaro Networking , Preeti U Murthy Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Preeti, On 23 April 2014 17:54, Preeti Murthy wrote: > On Wed, Apr 23, 2014 at 3:08 PM, Viresh Kumar wrote: > In case of high resolution mode, the clock device would have > already been programmed for the upcoming hrtimer, the last > time the list of hrtimers was evaluated. So we have > already taken care of hrtimers to expire next. I actually missed this part and things look correct with this. We aren't choosing the next device event here but just the next time we need tick. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/