Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752858AbdDLKSN (ORCPT ); Wed, 12 Apr 2017 06:18:13 -0400 Received: from mail-wr0-f177.google.com ([209.85.128.177]:36488 "EHLO mail-wr0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751876AbdDLKSJ (ORCPT ); Wed, 12 Apr 2017 06:18:09 -0400 Date: Wed, 12 Apr 2017 13:18:04 +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: <20170412101804.cxo6h472ns76ukgo@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170411140907.GD4021@tassilo.jf.intel.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 Content-Length: 896 Lines: 24 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. We're pretty late into release cycle. It would be nice to give the whole thing time in tip/master and -next before the merge window. Can I repost part 4? -- Kirill A. Shutemov