Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757804AbYFYM0h (ORCPT ); Wed, 25 Jun 2008 08:26:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755501AbYFYM03 (ORCPT ); Wed, 25 Jun 2008 08:26:29 -0400 Received: from www.tglx.de ([62.245.132.106]:34735 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754335AbYFYM02 (ORCPT ); Wed, 25 Jun 2008 08:26:28 -0400 Date: Wed, 25 Jun 2008 14:22:32 +0200 (CEST) From: Thomas Gleixner To: Michael Kerrisk cc: Ingo Molnar , lkml , Roman Zippel , john stultz , Bart Van Assche Subject: Re: When did High-Resolution Timers hit mainline? In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 789 Lines: 22 On Wed, 25 Jun 2008, Michael Kerrisk wrote: > > Hmm, that's a bit backwards. We changed the internal handling of those > > interfaces to hrtimers in 2.6.16, but the accuracy is still jiffies > > unless you have CONFIG_HIGH_RES_TIMERS enabled (which is only possible > > as of 2.6.21) and your system provides the necessary hardware. > > So then it's simply enough to say: > > Since Linux 2.6.17, Linux optionaly supports high-resolution timers > (configurable via CONFIG_HIGH_RES_TIMERS). > > right? Make this 2.6.21 :) Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/