[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1347461431.15764.49.camel@twins>
Date: Wed, 12 Sep 2012 16:50:31 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Stephane Eranian <eranian@...gle.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
"mingo@...e.hu" <mingo@...e.hu>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"Yan, Zheng" <zheng.z.yan@...el.com>,
Robert Richter <robert.richter@....com>
Subject: Re: [PATCH v2 2/3] perf: use hrtimer for event multiplexing
On Wed, 2012-09-12 at 16:48 +0200, Stephane Eranian wrote:
> On Wed, Sep 12, 2012 at 4:44 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> > On Wed, 2012-09-12 at 16:43 +0200, Stephane Eranian wrote:
> >> The hrtimer_active is used to prevent activating the timer multiple times
> >> in a row.
> >
> > see hrtimer_active(), this should do what you want I think.
>
> I need something that is true even when the hrtimer is not executing
> the callback handler. I guess that may be the different between
> hrtimer_active() vs. hrtimer_running()?
As the comment states, hrtimer_active() returns true if the timer is
either in the tree (enqueued) or running.
hrtimer_callback_running() is true iff the callback is currently
executing.
hrtimer_queued() is true iff the timer is queued.
--
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/
Powered by blists - more mailing lists