From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C0782C6778A for ; Tue, 3 Jul 2018 08:30:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 615A224658 for ; Tue, 3 Jul 2018 08:30:46 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 615A224658 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933299AbeGCIal (ORCPT ); Tue, 3 Jul 2018 04:30:41 -0400 Received: from mga03.intel.com ([134.134.136.65]:28970 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932169AbeGCIai (ORCPT ); Tue, 3 Jul 2018 04:30:38 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jul 2018 01:30:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,302,1526367600"; d="scan'208";a="54739315" Received: from black.fi.intel.com ([10.237.72.28]) by orsmga006.jf.intel.com with ESMTP; 03 Jul 2018 01:30:36 -0700 Received: by black.fi.intel.com (Postfix, from userid 1000) id B6A76F7; Tue, 3 Jul 2018 11:30:39 +0300 (EEST) Date: Tue, 3 Jul 2018 11:30:39 +0300 From: "Kirill A. Shutemov" To: Benjamin Gilbert Cc: linux-x86_64@vger.kernel.org, linux-kernel@vger.kernel.org, Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , x86@kernel.org Subject: Re: 4.17.x won't boot due to "x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G" Message-ID: <20180703083038.cxvyhq5vsxyeuyvu@black.fi.intel.com> References: <20180701213243.GA20180@trogon.sfo.coreos.systems> <20180702093450.h5tfjeynpi3nwjbo@black.fi.intel.com> <20180702190128.GA455@trogon.sfo.coreos.systems> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180702190128.GA455@trogon.sfo.coreos.systems> User-Agent: NeoMutt/20170714-126-deb55f (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 02, 2018 at 07:01:28PM +0000, Benjamin Gilbert wrote: > On Mon, Jul 02, 2018 at 12:34:50PM +0300, Kirill A. Shutemov wrote: > > Could you check if you can trigger the issue with my changes to config and > > the way I run KVM? > > Yes, the issue still triggers in that case. I've also verified that the > kernel boots normally with your qemu command if the commit is reverted. Hm. What toolchain do you use? -- Kirill A. Shutemov