Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263032AbUKTBWM (ORCPT ); Fri, 19 Nov 2004 20:22:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263077AbUKTBV6 (ORCPT ); Fri, 19 Nov 2004 20:21:58 -0500 Received: from bgm-24-95-139-53.stny.rr.com ([24.95.139.53]:60392 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S263032AbUKTBRv (ORCPT ); Fri, 19 Nov 2004 20:17:51 -0500 Subject: Re: smp_apic_timer_interrupt entry point From: Steven Rostedt To: Darren Hart Cc: LKML In-Reply-To: <1100911984.22670.4.camel@localhost.localdomain> References: <1100911984.22670.4.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Kihon Technologies Date: Fri, 19 Nov 2004 20:17:45 -0500 Message-Id: <1100913465.4051.48.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 876 Lines: 23 On Fri, 2004-11-19 at 16:53 -0800, Darren Hart wrote: > I am trying to hunt down the entry point to smp_apic_timer_interrupt() > for i386. grep found: > > arch/x86_64/kernel/entry.S: apicinterrupt LOCAL_TIMER_VECTOR,smp_apic_timer_interrupt > > but nothing for i386. I noticed that entry.o on i386 does contain the > string "smp_apic_timer_interrupt", is there some kind of linker magic > going on? Not linker magic, but macro magic. Look again at entry.S at BUILD_INTERRUPT. It adds the smp_ onto apic_timer_interrupt. Then look where apic_timer_interrupt is used. -- Steven Rostedt Senior Engineer Kihon Technologies - 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/