From: Michael Kerrisk <mtk-manpages@gmx.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Ulrich Drepper <drepper@redhat.com>,
geoff@gclare.org.uk, lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@xenotime.net>,
vda.linux@googlemail.com,
Linus Torvalds <torvalds@linux-foundation.org>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
david@hardeman.nu
Subject: Re: RFC: A revised timerfd API
Date: Sun, 23 Sep 2007 21:03:00 +0200 [thread overview]
Message-ID: <46F6B864.9080902@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0709231138260.22989@alien.or.mcafeemobile.com>
Davide Libenzi wrote:
> On Sun, 23 Sep 2007, Davide Libenzi wrote:
>
>> On Sun, 23 Sep 2007, Michael Kerrisk wrote:
>>
>>> I applied this patch against 2.6.27-rc7, and wired up the syscalls as shown
>>> in the definitions below. When I ran the the program below, my system
>>> immediately froze. Can you try it on your system please.
>> There's an hrtimer_init() missing in timerfd_create(). I'll refactor the
>> patch.
>
> There's the case of a timerfd_gettime return status when the timerfd has
> not been set yet (ie, soon after a timerfd_create), to handle.
> Current way is to return an (itimerspec) { 0, 0 }. Ok?
Seems reasonable. In the analogous situation, the POSIX timers API
returns a structure containing all zeros, at least on Linux.
prev parent reply other threads:[~2007-09-23 19:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 7:27 RFC: A revised timerfd API Michael Kerrisk
2007-09-18 7:30 ` Michael Kerrisk
2007-09-18 8:05 ` David Härdeman
2007-09-18 9:01 ` Michael Kerrisk
2007-09-18 9:27 ` Thomas Gleixner
2007-09-18 9:10 ` Thomas Gleixner
2007-09-18 9:30 ` Michael Kerrisk
2007-09-18 9:42 ` Thomas Gleixner
2007-09-18 11:08 ` Michael Kerrisk
2007-09-18 11:30 ` Thomas Gleixner
2007-09-18 13:13 ` David Härdeman
2007-09-22 13:03 ` Michael Kerrisk
2007-09-18 16:51 ` Davide Libenzi
2007-09-22 13:12 ` Michael Kerrisk
2007-09-22 14:32 ` Bernd Eckenfels
2007-09-22 16:07 ` Michael Kerrisk
2007-09-22 17:05 ` Thomas Gleixner
2007-09-22 23:37 ` David Härdeman
2007-09-22 17:10 ` Thomas Gleixner
2007-09-22 21:07 ` Davide Libenzi
2007-09-22 21:26 ` Thomas Gleixner
2007-09-22 23:21 ` Davide Libenzi
2007-09-23 17:33 ` Michael Kerrisk
2007-09-23 18:33 ` Davide Libenzi
2007-09-23 18:41 ` Davide Libenzi
2007-09-23 19:03 ` Michael Kerrisk [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=46F6B864.9080902@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@hardeman.nu \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=geoff@gclare.org.uk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
/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