linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Preeti Murthy <preeti.lkml@gmail.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Lists linaro-kernel" <linaro-kernel@lists.linaro.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linaro Networking" <linaro-networking@linaro.org>,
	"Preeti U Murthy" <preeti@linux.vnet.ibm.com>
Subject: Re: [Query]: hrtimers: why don't we consider hrtimers in get_next_timer_interrupt()
Date: Thu, 24 Apr 2014 10:13:56 +0530	[thread overview]
Message-ID: <CAKohpomHgtow=L8CQ8XA6NrXza1g9k0j2by-GR2erB4=7Oexhg@mail.gmail.com> (raw)
In-Reply-To: <CAM4v1pMRiWkUx0YboOkcYXDt=quXiR7FWs0b=HjzbRG+sdnPFA@mail.gmail.com>

Hi Preeti,

On 23 April 2014 17:54, Preeti Murthy <preeti.lkml@gmail.com> wrote:
> On Wed, Apr 23, 2014 at 3:08 PM, Viresh Kumar <viresh.kumar@linaro.org> 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.

      reply	other threads:[~2014-04-24  4:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  9:38 [Query]: hrtimers: why don't we consider hrtimers in get_next_timer_interrupt() Viresh Kumar
2014-04-23 12:24 ` Preeti Murthy
2014-04-24  4:43   ` Viresh Kumar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKohpomHgtow=L8CQ8XA6NrXza1g9k0j2by-GR2erB4=7Oexhg@mail.gmail.com' \
    --to=viresh.kumar@linaro.org \
    --cc=fweisbec@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linaro-networking@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preeti.lkml@gmail.com \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).