From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262754AbTI1Vke (ORCPT ); Sun, 28 Sep 2003 17:40:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262758AbTI1Vke (ORCPT ); Sun, 28 Sep 2003 17:40:34 -0400 Received: from fw.osdl.org ([65.172.181.6]:42158 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262754AbTI1Vkd (ORCPT ); Sun, 28 Sep 2003 17:40:33 -0400 Date: Sun, 28 Sep 2003 14:41:02 -0700 From: Andrew Morton To: Geert Uytterhoeven Cc: oliver@linux-kernel.at, torvalds@osdl.org, linux-kernel@vger.kernel.org Subject: Re: Linux 2.6.0-test6 Message-Id: <20030928144102.5097ad81.akpm@osdl.org> In-Reply-To: References: <200309281216.h8SCGWsl026399@indianer.linux-kernel.at> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Geert Uytterhoeven wrote: > > There's a new architecture-specific routine sched_clock() to be implemented > (which was BTW not announced on the secret all-architectures mail alias ;-). Was too! On September 18. I considered providing a default implementation, but really, if the hardware has a higher resolution timer then sched_clock() should use that. Providing a HZ-based default would lessen the likelihood of the Alpha developers doing this properly.