Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270411AbUJUIeK (ORCPT ); Thu, 21 Oct 2004 04:34:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270595AbUJUId7 (ORCPT ); Thu, 21 Oct 2004 04:33:59 -0400 Received: from fmr05.intel.com ([134.134.136.6]:11240 "EHLO hermes.jf.intel.com") by vger.kernel.org with ESMTP id S270411AbUJUIdS convert rfc822-to-8bit (ORCPT ); Thu, 21 Oct 2004 04:33:18 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Subject: RE: gradual timeofday overhaul Date: Thu, 21 Oct 2004 01:32:53 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: gradual timeofday overhaul Thread-Index: AcS2wTYVfOEhvEjFTvCHP5zy7UEl+AAU9ouA From: "Perez-Gonzalez, Inaky" To: , "George Anzinger" Cc: "Brown, Len" , "Tim Schmielau" , "john stultz" , "lkml" X-OriginalArrivalTime: 21 Oct 2004 08:32:54.0143 (UTC) FILETIME=[8F3610F0:01C4B748] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 878 Lines: 23 > From: Richard B. Johnson > > You need that hardware interrupt for more than time-keeping. > Without a hardware-interrupt, to force a new time-slice, > > for(;;) > ; > > ... would allow a user to grab the CPU forever ... But you can also schedule, before switching to the new task, a local interrupt on the running processor to mark the end of the timeslice. When you enter the scheduler, you just need to remove that; devil is in the details, but it should be possible to do in a way that doesn't take too much overhead. I?aky P?rez-Gonz?lez -- Not speaking for Intel -- all opinions are my own (and my fault) - 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/