Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262830AbUKTAz5 (ORCPT ); Fri, 19 Nov 2004 19:55:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261720AbUKTAxh (ORCPT ); Fri, 19 Nov 2004 19:53:37 -0500 Received: from e5.ny.us.ibm.com ([32.97.182.105]:39335 "EHLO e5.ny.us.ibm.com") by vger.kernel.org with ESMTP id S262743AbUKTAwp (ORCPT ); Fri, 19 Nov 2004 19:52:45 -0500 Subject: smp_apic_timer_interrupt entry point From: Darren Hart To: linux-kernel@vger.kernel.org Content-Type: text/plain Date: Fri, 19 Nov 2004 16:53:04 -0800 Message-Id: <1100911984.22670.4.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 628 Lines: 19 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? Thanks, -- Darren Hart - 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/