linux-kernel - Re: [Query]: hrtimers: why don't we consider hrtimers in get_next_timer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 24 Apr 2014 10:13:56 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Preeti Murthy <preeti.lkml@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linaro Networking <linaro-networking@...aro.org>,
	Preeti U Murthy <preeti@...ux.vnet.ibm.com>
Subject: Re: [Query]: hrtimers: why don't we consider hrtimers in get_next_timer_interrupt()

Hi Preeti,

On 23 April 2014 17:54, Preeti Murthy <preeti.lkml@...il.com> wrote:
> On Wed, Apr 23, 2014 at 3:08 PM, Viresh Kumar <viresh.kumar@...aro.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/