From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f199.google.com (mail-io0-f199.google.com [209.85.223.199]) by kanga.kvack.org (Postfix) with ESMTP id 0111B800D8 for ; Tue, 23 Jan 2018 12:31:18 -0500 (EST) Received: by mail-io0-f199.google.com with SMTP id d62so1352885iof.8 for ; Tue, 23 Jan 2018 09:31:17 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id o6sor10240190iod.203.2018.01.23.09.31.17 for (Google Transport Security); Tue, 23 Jan 2018 09:31:17 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20180123170913.41791-5-kirill.shutemov@linux.intel.com> References: <20180123170913.41791-1-kirill.shutemov@linux.intel.com> <20180123170913.41791-5-kirill.shutemov@linux.intel.com> From: Linus Torvalds Date: Tue, 23 Jan 2018 09:31:16 -0800 Message-ID: Subject: Re: [PATCHv6, RESEND 4/4] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: "Kirill A. Shutemov" Cc: 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 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"? Linus -- 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