From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932529AbdDRI7n (ORCPT ); Tue, 18 Apr 2017 04:59:43 -0400 Received: from mail-wr0-f193.google.com ([209.85.128.193]:34213 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755382AbdDRI7a (ORCPT ); Tue, 18 Apr 2017 04:59:30 -0400 Date: Tue, 18 Apr 2017 11:59:26 +0300 From: "Kirill A. Shutemov" To: Ingo Molnar Cc: Andi Kleen , "Kirill A. Shutemov" , Andy Lutomirski , Linus Torvalds , Andrew Morton , x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Dave Hansen , linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/8] x86/boot/64: Add support of additional page table level during early boot Message-ID: <20170418085926.bzdzs2wwxjmdxqxm@node.shutemov.name> References: <20170406140106.78087-1-kirill.shutemov@linux.intel.com> <20170406140106.78087-4-kirill.shutemov@linux.intel.com> <20170411070203.GA14621@gmail.com> <20170411105106.4zgbzuu4s4267zyv@node.shutemov.name> <20170411112845.GA15212@gmail.com> <20170411114616.otx2f6aw5lcvfc2o@black.fi.intel.com> <20170411140907.GD4021@tassilo.jf.intel.com> <20170412101804.cxo6h472ns76ukgo@node.shutemov.name> <20170417103225.ycv73fdrfx33e5sd@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170417103225.ycv73fdrfx33e5sd@gmail.com> User-Agent: NeoMutt/20170306 (1.8.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 17, 2017 at 12:32:25PM +0200, Ingo Molnar wrote: > > * Kirill A. Shutemov wrote: > > > On Tue, Apr 11, 2017 at 07:09:07AM -0700, Andi Kleen wrote: > > > > I'll look closer (building proccess it's rather complicated), but my > > > > understanding is that VDSO is stand-alone binary and doesn't really links > > > > with the rest of the kernel, rather included as blob, no? > > > > > > > > Andy, may be you have an idea? > > > > > > There isn't any way I know of to directly link them together. The ELF > > > format wasn't designed for that. You would need to merge blobs and then use > > > manual jump vectors, like the 16bit startup code does. It would be likely > > > complicated and ugly. > > > > Ingo, can we proceed without coverting this assembly to C? > > > > I'm committed to convert it to C later if we'll find reasonable solution > > to the issue. > > So one way to do it would be to build it standalone as a .o, then add it not to > the regular kernel objects link target (as you found out it's not possible to link > 32-bit and 64-bit objects), but to link it in a manual fashion, as part of > vmlinux.bin.all-y in arch/x86/boot/compressed/Makefile. > > But there would be other complications with this approach, such as we'd have to > add a size field and there might be symbol linking problems ... > > Another, pretty hacky way would be to generate a .S from the .c, then post-process > the .S and essentially generate today's 32-bit .S from it. > > Probably not worth the trouble. So, do I need to do anything else to get part 4 applied? -- Kirill A. Shutemov From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kirill A. Shutemov" Subject: Re: [PATCH 3/8] x86/boot/64: Add support of additional page table level during early boot Date: Tue, 18 Apr 2017 11:59:26 +0300 Message-ID: <20170418085926.bzdzs2wwxjmdxqxm@node.shutemov.name> References: <20170406140106.78087-1-kirill.shutemov@linux.intel.com> <20170406140106.78087-4-kirill.shutemov@linux.intel.com> <20170411070203.GA14621@gmail.com> <20170411105106.4zgbzuu4s4267zyv@node.shutemov.name> <20170411112845.GA15212@gmail.com> <20170411114616.otx2f6aw5lcvfc2o@black.fi.intel.com> <20170411140907.GD4021@tassilo.jf.intel.com> <20170412101804.cxo6h472ns76ukgo@node.shutemov.name> <20170417103225.ycv73fdrfx33e5sd@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170417103225.ycv73fdrfx33e5sd@gmail.com> Sender: owner-linux-mm@kvack.org To: Ingo Molnar Cc: Andi Kleen , "Kirill A. Shutemov" , Andy Lutomirski , Linus Torvalds , Andrew Morton , x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Dave Hansen , linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org List-Id: linux-arch.vger.kernel.org On Mon, Apr 17, 2017 at 12:32:25PM +0200, Ingo Molnar wrote: > > * Kirill A. Shutemov wrote: > > > On Tue, Apr 11, 2017 at 07:09:07AM -0700, Andi Kleen wrote: > > > > I'll look closer (building proccess it's rather complicated), but my > > > > understanding is that VDSO is stand-alone binary and doesn't really links > > > > with the rest of the kernel, rather included as blob, no? > > > > > > > > Andy, may be you have an idea? > > > > > > There isn't any way I know of to directly link them together. The ELF > > > format wasn't designed for that. You would need to merge blobs and then use > > > manual jump vectors, like the 16bit startup code does. It would be likely > > > complicated and ugly. > > > > Ingo, can we proceed without coverting this assembly to C? > > > > I'm committed to convert it to C later if we'll find reasonable solution > > to the issue. > > So one way to do it would be to build it standalone as a .o, then add it not to > the regular kernel objects link target (as you found out it's not possible to link > 32-bit and 64-bit objects), but to link it in a manual fashion, as part of > vmlinux.bin.all-y in arch/x86/boot/compressed/Makefile. > > But there would be other complications with this approach, such as we'd have to > add a size field and there might be symbol linking problems ... > > Another, pretty hacky way would be to generate a .S from the .c, then post-process > the .S and essentially generate today's 32-bit .S from it. > > Probably not worth the trouble. So, do I need to do anything else to get part 4 applied? -- Kirill A. Shutemov -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org