From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263340AbVGORyY (ORCPT ); Fri, 15 Jul 2005 13:54:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263349AbVGORyY (ORCPT ); Fri, 15 Jul 2005 13:54:24 -0400 Received: from pollux.ds.pg.gda.pl ([153.19.208.7]:18702 "EHLO pollux.ds.pg.gda.pl") by vger.kernel.org with ESMTP id S263340AbVGORyW (ORCPT ); Fri, 15 Jul 2005 13:54:22 -0400 Date: Fri, 15 Jul 2005 18:54:30 +0100 (BST) From: "Maciej W. Rozycki" To: Venkatesh Pallipadi Cc: Andi Kleen , "Brown, Len" , akpm@osdl.org, linux-kernel@vger.kernel.org, torvalds@osdl.org, vojtech@suse.cz, christoph@lameter.com Subject: Re: [PATCH] i386: Selectable Frequency of the Timer Interrupt In-Reply-To: <20050715102349.A15791@unix-os.sc.intel.com> Message-ID: References: <20050715102349.A15791@unix-os.sc.intel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 15 Jul 2005, Venkatesh Pallipadi wrote: > I wouldn't say it is totally impossible. There are ways in which Linux can work > without a reliable Local APIC timer. One option being - make one CPU that gets > the external timer interrupt multicast an IPI to all the other CPUs that > wants to get periodic timer interrupt. That's like scratching your left ear with your right hand -- broadcasting that external timer interrupt in the first place is more straightforward. If you want to exclude CPUs from the list of receivers, just use the logical destination mode appropriately. Maciej