From: "H. Peter Anvin" Subject: Re: [RFC v1 5/8] x86/init: move ebda reservations into linker table Date: Thu, 17 Dec 2015 12:55:14 -0800 Message-ID: <56732132.4080401@zytor.com> References: <1450217797-19295-1-git-send-email-mcgrof@do-not-panic.com> <1450217797-19295-6-git-send-email-mcgrof@do-not-panic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski , "Luis R. Rodriguez" Cc: 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, Luis Rodriguez , X86 ML , Xen Devel , "linux-kernel@vger.kernel.org" List-Id: xen-devel@lists.xenproject.org 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. -hpa