Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761410AbYBLBUX (ORCPT ); Mon, 11 Feb 2008 20:20:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757242AbYBLBUI (ORCPT ); Mon, 11 Feb 2008 20:20:08 -0500 Received: from waste.org ([66.93.16.53]:59994 "EHLO waste.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754006AbYBLBUG (ORCPT ); Mon, 11 Feb 2008 20:20:06 -0500 Subject: Re: [PATCH] x86 (Linux Tiny): configure out support for some processors From: Matt Mackall To: "H. Peter Anvin" Cc: Michael Opdenacker , Ingo Molnar , Andrew Morton , Thomas Gleixner , linux-kernel@vger.kernel.org, Linux-tiny@selenic.com In-Reply-To: <47B0EE46.6050208@zytor.com> References: <200802082347.25364.michael-lists@free-electrons.com> <20080208231130.GA10511@elte.hu> <200802112342.23493.michael-lists@free-electrons.com> <1202770566.12383.59.camel@cinder.waste.org> <47B0D3B7.6070308@zytor.com> <1202772532.12383.67.camel@cinder.waste.org> <47B0EE46.6050208@zytor.com> Content-Type: text/plain Date: Mon, 11 Feb 2008 19:15:20 -0600 Message-Id: <1202778920.12383.74.camel@cinder.waste.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1608 Lines: 42 On Mon, 2008-02-11 at 16:54 -0800, H. Peter Anvin wrote: > Matt Mackall wrote: > > On Mon, 2008-02-11 at 15:01 -0800, H. Peter Anvin wrote: > >> Matt Mackall wrote: > >>> Best would be to have no ifdefs and do it all with linker magic, of > >>> course. But that's trickier. > >>> > >> I concur with this, definitely. > > > > Ok, so let's come up with a plan. We can: > > > > a) use weak symbols, ala cond_syscall > > b) use a special section > > c) use early_init code (is it early enough?) > > c) have some sort of registration list > > > > Having a generic cond_call of some sort might be nice for this sort of > > thing. > > > > c) is out, because this has to be executed after the early generic code > and before the late generic code. > > b) would be my first choice, and yes, it would be a good thing to have a > generalized mechanism for this. For the registrant, it's pretty easy: > just add a macro that adds a pointer to a named section. We then need a > way to get the base address and length of each such section in order to > be able to execute each function in sequence. I like the idea of making a generalized hook section. But this is a bit burdensome for Michael's little patch (unless you have time to whip something up) so I think we should probably explore it separately. -- Mathematics is the supreme nostalgia of our time. -- 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/