From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751547AbeAWRhI (ORCPT ); Tue, 23 Jan 2018 12:37:08 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:39202 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751259AbeAWRhG (ORCPT ); Tue, 23 Jan 2018 12:37:06 -0500 X-Google-Smtp-Source: AH8x2245NtLClaaAAv2vxWmQuroAv4Iu8Bb0NtvS8B/SiWvLQ0I8wl01WS/W0tchQsQEOz7Hk/dsHg== Date: Tue, 23 Jan 2018 20:37:03 +0300 From: "Kirill A. Shutemov" To: Linus Torvalds Cc: "Kirill A. Shutemov" , Ingo Molnar , the arch/x86 maintainers , Thomas Gleixner , "H. Peter Anvin" , Andy Lutomirski , Cyrill Gorcunov , Borislav Petkov , Andi Kleen , linux-mm , Linux Kernel Mailing List Subject: Re: [PATCHv6, RESEND 4/4] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G Message-ID: <20180123173703.rrr7igl7xtlsawhf@node.shutemov.name> References: <20180123170913.41791-1-kirill.shutemov@linux.intel.com> <20180123170913.41791-5-kirill.shutemov@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 23, 2018 at 09:31:16AM -0800, Linus Torvalds wrote: > On Tue, Jan 23, 2018 at 9:09 AM, Kirill A. Shutemov > wrote: > > > > But if the bootloader put the kernel above 4G (not sure if anybody does > > this), we would lose control as soon as paging is disabled, because the > > code becomes unreachable to the CPU. > > I do wonder if we need this. Why would a bootloader ever put the data > above 4G? Does this really happen? Wouldn't it be easier to just say > "bootloaders better put the kernel in the low 4G"? I don't know much about bootloaders, but do we even have such guarantee for in-kernel bootloader -- kexec? -- Kirill A. Shutemov