From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mike Galbraith <efault@gmx.de>, Oleg Nesterov <oleg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Michael Kerrisk <mtk.manpages@googlemail.com>
Subject: Re: [PATCH] timers: fix TIMER_ABSTIME for process wide cpu timers
Date: Wed, 11 Feb 2009 13:52:40 +0100 [thread overview]
Message-ID: <20090211125240.GJ16535@elte.hu> (raw)
In-Reply-To: <1234349601.23438.125.camel@twins>
* Peter Zijlstra <peterz@infradead.org> wrote:
> While going through the man-pages Michael prepared for the posix timer
> interface I realized that posix timers do expose the absolute time value
> through the use of TIMER_ABSTIME.
>
> ---
> Subject: timers: fix TIMER_ABSTIME for process wide cpu timers
> From: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Wed Feb 11 11:30:27 CET 2009
>
> The POSIX timer interface allows for absolute time expiry values through the
> TIMER_ABSTIME flag, therefore we have to synchronize the timer to the clock
> every time we start it.
>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Applied to tip:timers/urgent, thanks Peter!
Ingo
next prev parent reply other threads:[~2009-02-11 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 8:56 x86-tip.today: flood of WARNING: at include/linux/sched.h:2238 run_posix_cpu_timers+0xea/0x79f() Mike Galbraith
2009-02-06 14:01 ` Ingo Molnar
2009-02-10 15:37 ` Peter Zijlstra
2009-02-11 10:53 ` [PATCH] timers: fix TIMER_ABSTIME for process wide cpu timers Peter Zijlstra
2009-02-11 12:52 ` Ingo Molnar [this message]
2009-02-11 12:53 ` x86-tip.today: flood of WARNING: at include/linux/sched.h:2238 run_posix_cpu_timers+0xea/0x79f() Ingo Molnar
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=20090211125240.GJ16535@elte.hu \
--to=mingo@elte.hu \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®