mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: mtk.manpages@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 2/2] timerfd extend clockid support
Date: Mon, 9 Feb 2009 09:42:41 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.1.10.0902090940100.8084@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <cfd18e0f0902090128i1a4902f4of0d4d830b567602f@mail.gmail.com>

On Mon, 9 Feb 2009, Michael Kerrisk wrote:

> On Mon, Feb 9, 2009 at 12:23 PM, Davide Libenzi <davidel@xmailserver.org> wrote:
> > The following patch extends timerfd clockid support to cover the ones
> > supported by timer_create().
> > It exports the invalid_clockid() function outside posix-timers.c to allow
> > timerfd to properly check input parameters.
> > Andrew, this is (eventually) .30 material, and do not take the patch
> > until you have Thomas sign off.
> > Thomas, timerfd uses core hrtimer functions for its tasks. By extending
> > the clockid support, I assume that the clockids other than CLOCK_MONOTONIC
> > and CLOCK_REALTIME, behaves the same from a hrtimer caller POV. Right?
> 
> Hi Davide,
> 
> Have you done any testing of this patch?  My attempts at testing with
> clocks other than REALTIME and MONOTONIC all don't work so far.  In
> some cases, my test programs causes the system to hang.  Try
> experimenting with the (not yet well tested) test program below, to
> check the behavior with other clocks.

Michael, no I did not test it and I did not have even the time to peek 
into the core timer code to see if the usage of other timer types in 
eventfd would create problems. That's why I asked Thomas if they'd behave 
differently from an hrtimer caller POV.
I'll try to take a look by myself today or tomorrow.


- Davide



  reply	other threads:[~2009-02-09 17:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 23:23 Davide Libenzi
2009-02-09  9:28 ` Michael Kerrisk
2009-02-09 17:42   ` Davide Libenzi [this message]
2009-02-09 19:28     ` Michael Kerrisk
2009-02-09 20:10       ` Davide Libenzi
2009-02-09 23:01         ` Michael Kerrisk
2009-02-09 23:03         ` Michael Kerrisk
2009-02-09 23:23           ` Davide Libenzi
2009-02-09 23:25             ` Michael Kerrisk

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=alpine.DEB.1.10.0902090940100.8084@alien.or.mcafeemobile.com \
    --to=davidel@xmailserver.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.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

all inboxes | Powered by JetHome®