Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261932AbVDGHqH (ORCPT ); Thu, 7 Apr 2005 03:46:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261916AbVDGHqG (ORCPT ); Thu, 7 Apr 2005 03:46:06 -0400 Received: from 71-33-33-84.albq.qwest.net ([71.33.33.84]:48828 "EHLO montezuma.fsmlabs.com") by vger.kernel.org with ESMTP id S261997AbVDGHpw (ORCPT ); Thu, 7 Apr 2005 03:45:52 -0400 Date: Thu, 7 Apr 2005 01:47:50 -0600 (MDT) From: Zwane Mwaikambo To: Magnus Damm cc: Malcolm Rowe , linux-kernel@vger.kernel.org Subject: Re: [PATCH][RFC] disable built-in modules V2 In-Reply-To: Message-ID: References: <20050405225747.15125.8087.59570@clementine.local> 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 Content-Length: 1314 Lines: 31 On Thu, 7 Apr 2005, Magnus Damm wrote: > On Apr 6, 2005 4:28 PM, Malcolm Rowe wrote: > > Magnus Damm writes: > > > And I guess the idea of replacing the initcall pointer with NULL will > > > work both with and without function descriptors, right? So we should > > > be safe on IA64 and PPC64. > > > > I think so, though I don't really know a great deal about this area. > > > > An IA64 descriptor is of the form { &code, &data_context }, and a function > > pointer is a pointer to such a descriptor. Presumably, setting a function > > pointer to NULL will either end up setting the pointer-to-descriptor to NULL > > or the code pointer to NULL, but either way, I would expect the 'if > > (!*call)' comparison to work as intended. > > > > Best thing would be to get someone on IA64 and/or PPC64 to check this for > > you. > > I agree. Do we have any friendly IA64/PPC64 user out there? In C code it is consistent across all architectures, you only have to worry about the descriptors when you do modifications in assembly. Zwane - 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/