Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754150AbbLQXkO (ORCPT ); Thu, 17 Dec 2015 18:40:14 -0500 Received: from mx2.suse.de ([195.135.220.15]:49534 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751991AbbLQXkM (ORCPT ); Thu, 17 Dec 2015 18:40:12 -0500 Date: Fri, 18 Dec 2015 00:40:07 +0100 From: "Luis R. Rodriguez" To: Andy Lutomirski Cc: "H. Peter Anvin" , "Luis R. Rodriguez" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Konrad Rzeszutek Wilk , Rusty Russell , Boris Ostrovsky , mcb30@ipxe.org, Juergen Gross , Jan Beulich , Joerg Roedel , Andrey Ryabinin , Andrey Konovalov , long.wanglong@huawei.com, qiuxishi@huawei.com, Andrey Ryabinin , Mauro Carvalho Chehab , valentinrothberg@gmail.com, peter.senna@gmail.com, Michal Marek , X86 ML , Xen Devel , "linux-kernel@vger.kernel.org" Subject: Re: [RFC v1 5/8] x86/init: move ebda reservations into linker table Message-ID: <20151217234007.GW20409@wotan.suse.de> References: <1450217797-19295-1-git-send-email-mcgrof@do-not-panic.com> <1450217797-19295-6-git-send-email-mcgrof@do-not-panic.com> <56732132.4080401@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1302 Lines: 31 On Thu, Dec 17, 2015 at 12:57:49PM -0800, Andy Lutomirski wrote: > On Thu, Dec 17, 2015 at 12:55 PM, H. Peter Anvin wrote: > > On 12/17/15 12:48, Andy Lutomirski wrote: > >> > >> I'm entirely ignorant of anything going on in gPXE/iPXE. > >> > >> Can you explain what a linker table *does*? It looks like all you've > >> done in this patch is to move code around. What actually happens? > >> > > > > A linker table is a data structure that is stitched together from items > > in multiple object files. > > > > We already have a *bunch* of linker tables in Linux, mostly the init > > tables, but they are all built in an ad hoc manner which requires linker > > script modifications, which are of course per architecture. > > > > My desire would be to make a general linker table facility so that a new > > linker table can be implemented by changing C code only. > > Sounds good to me. That's what this actually accomplishes, there are just a few caveats to consider, more on this shortly on the other thread in this patch series. Luis -- 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/