From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756107AbZBIXDk (ORCPT ); Mon, 9 Feb 2009 18:03:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753958AbZBIXDb (ORCPT ); Mon, 9 Feb 2009 18:03:31 -0500 Received: from wa-out-1112.google.com ([209.85.146.177]:10341 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753447AbZBIXDa (ORCPT ); Mon, 9 Feb 2009 18:03:30 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=bjhcABu83APqzklhxsy+B3SX+hjV2VrdnuxoOutg1LNz/Zpg9Nlxr9PV7yeYwemTaa k3AlsakyBxJJel00ET46k0629MPM6N90G7J69qOrxHgsi5ekGWcSc2kAes8FWC+6fj6o UJmSjSLLGvEnJ6tADviZv4wDb7R++ZzmxCQs8= MIME-Version: 1.0 Reply-To: mtk.manpages@gmail.com In-Reply-To: References: Date: Tue, 10 Feb 2009 12:03:28 +1300 Message-ID: Subject: Re: [patch 2/2] timerfd extend clockid support From: Michael Kerrisk To: Davide Libenzi Cc: Linux Kernel Mailing List , Thomas Gleixner , Andrew Morton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 10, 2009 at 9:10 AM, Davide Libenzi wrote: > On Tue, 10 Feb 2009, Michael Kerrisk wrote: > >> > 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. >> >> Okay -- hopefully my test program may be useful (even if it is not >> itself fully tested yet, it's patterned after a similar test program I >> wrote fot the POSIX timers API, so it should mostly work). > > Answer was pretty easy once you look at the code :) > Timerfd uses core hrtimer functions, and clockids different from the ones > timerfd already handles, fall into the CPU-timers domain. Domain that is > not handled by hrtimer. > Changes to timerfd to support CPU-based timers are really deep (more than > changes, is a total rewrite). not only to timerfd, but also to CPU-based > timers to deliver notification by means different than signals. > Given the amount of code change, and given that a posix-timers->signalfd > bridge could solve the problem, I'm not going even close to suggest such a > change. Davide, Will you nevertheless push the patch that adds the EINVAL flags checks? Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html