Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262480AbVA0CBn (ORCPT ); Wed, 26 Jan 2005 21:01:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261836AbVAZXqr (ORCPT ); Wed, 26 Jan 2005 18:46:47 -0500 Received: from e34.co.us.ibm.com ([32.97.110.132]:18106 "EHLO e34.co.us.ibm.com") by vger.kernel.org with ESMTP id S262035AbVAZTPd (ORCPT ); Wed, 26 Jan 2005 14:15:33 -0500 Subject: Re: [PATCH] unexport register_cpu and unregister_cpu From: Nathan Lynch To: Keshavamurthy Anil S Cc: lkml , Andrew Morton In-Reply-To: <20050126102226.A27022@unix-os.sc.intel.com> References: <1106722547.9855.36.camel@localhost.localdomain> <20050126102226.A27022@unix-os.sc.intel.com> Content-Type: text/plain Date: Wed, 26 Jan 2005 13:10:30 -0600 Message-Id: <1106766630.13753.23.camel@biclops> Mime-Version: 1.0 X-Mailer: Evolution 2.1.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1751 Lines: 38 On Wed, 2005-01-26 at 10:22 -0800, Keshavamurthy Anil S wrote: > On Wed, Jan 26, 2005 at 12:55:47AM -0600, Nathan Lynch wrote: > > http://linus.bkbits.net:8080/linux-2.5/cset@4180a2b7mi2fzuNQDBOQY7eMAkns8g?nav=index.html|src/|src/drivers|src/drivers/base|related/drivers/base/cpu.c > > > > This changeset introduced exports for register_cpu and unregister_cpu > > right after 2.6.10. As far as I can tell these are not called from any > > code which can be built as a module, and I can't think of a good reason > > why any out of tree code would use them. Unless I've missed something, > > can we remove them before 2.6.11? > > No this is not correct. ACPI processor.ko driver which supports > physical CPU hotplug needs register_cpu() and unregister_cpu() functions > for dynamically hotadd/hotremove support of the processors. I do not understand your objection. The processor module does not call the interfaces in question directly. They are called only from arch setup code (e.g. arch/ia64/kernel/topology.c) which is never built as a module. > Please see drivers/acpi/processor_core.c > acpi_processor_hotadd_init() -> arch_register_cpu() -> > ->register_cpu(). Sure -- the arch_register_cpu and arch_unregister_cpu symbols need to be exported for this use (and they are). Exporting register_cpu and unregister_cpu is unnecessary. I double-checked an ia64 build with CONFIG_ACPI_HOTPLUG_CPU=y and CONFIG_ACPI_PROCESSOR=m and saw no errors or warnings caused by the change... Nathan - 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/