Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2217809imm; Mon, 3 Sep 2018 23:40:04 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYTQR3Xv6TWqblJwbjH1PQFLPVgQp/BXZZzhWan7LPfLveklMjZBExXyFb20ix0kduuo3QP X-Received: by 2002:a63:5756:: with SMTP id h22-v6mr18341332pgm.423.1536043204628; Mon, 03 Sep 2018 23:40:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536043204; cv=none; d=google.com; s=arc-20160816; b=Db5abmGjxXN0Yf2fe/f8S9duPGAXva6LUxq7orwnQQ/e0BpH31UhLU6mYOmO0uJvhi TYrRZ/mlBFC+wzyUrxFhaVzc7T5kgrNg7SaRHcNgFL+w4/PgixYpG/4TSnRrSRNd9L24 M/uBVHv7W/4mj8jzjXry2a6/4FQ9NsAmgl8OGCtvtWYUcQp/oSELVG0A5IiQjv0b1Jmp l3Ubk+43Fk4faUJSzvP9xFukSn2kc0X8/xprAtOZ59ndDbTuHMrRaZzVIQUVokDcvJci bTM2gdFjFqF66IuE0b5aYS1dNHYHeG4Qe0a90P2zt/i2HfnXRWkmlZyggDJzaqvliXYJ PIPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=FkoZ2ayrc4ONy/UDMF2EaeDn872d+80bmZDUaE61krM=; b=uYbjUM712VD9AcFzc1kM17T7VbTtqque9XLHRf603C7C5/CApKkG0Yfy5N/K73AdHs dhAwjC5wzNW514KLnK7VrCzvnMpobEKVUaSv0YhToPumYreZtppLmBVi58m9dZadFUYk 2rjbmkd0t7WAWU4b9CgvwfDmWm5s42OzydF95bpksCH1hXovZWqQNojY4K2F/R6an4ti sx+P77SXYG2E7wD5B0UAu++iOSKfEDXTDaM9vLhLEw6q6zCNSZiNeSO63JP28wPTfvX/ HsE5Y4eu11823VuS/zIzdYKj2au590P0aEZLFAaeKroiWgy8nd4mwV1AtwpPpTE14xOh jNmQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 9-v6si17310743pgf.599.2018.09.03.23.39.49; Mon, 03 Sep 2018 23:40:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727509AbeIDLCY (ORCPT + 99 others); Tue, 4 Sep 2018 07:02:24 -0400 Received: from terminus.zytor.com ([198.137.202.136]:36881 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726016AbeIDLCY (ORCPT ); Tue, 4 Sep 2018 07:02:24 -0400 Received: from carbon-x1.hos.anvin.org (c-24-5-245-234.hsd1.ca.comcast.net [24.5.245.234] (may be forged)) (authenticated bits=0) by mail.zytor.com (8.15.2/8.15.2) with ESMTPSA id w846aGBP3587245 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 3 Sep 2018 23:36:17 -0700 Subject: Re: [PATCH 1/3] x86/boot: Add bit fields into xloadflags for 5-level kernel checking To: Baoquan He , kirill.shutemov@linux.intel.com Cc: x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@kernel.org References: <20180829141624.13985-1-bhe@redhat.com> <20180829141624.13985-2-bhe@redhat.com> <6ea94875-ae07-6220-eb3e-d3f830cdac03@zytor.com> <20180904034414.GI1740@192.168.1.3> <4546fc39-4982-4c91-c812-0df1e9bc9e20@zytor.com> <20180904052036.GJ1740@192.168.1.3> <20180904060649.GK1740@192.168.1.3> From: "H. Peter Anvin" Message-ID: <44fc1530-eb88-d8c5-7465-e48c91799a98@zytor.com> Date: Mon, 3 Sep 2018 23:36:11 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180904060649.GK1740@192.168.1.3> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/03/18 23:06, Baoquan He wrote: >> >> That makes no sense. I'm talking about *entering* the kernel; the second >> kernel should switch to 5-level mode as necessary. > > OK, I didn't get your point. I forget what difficulty was met so that > Kirill need to take this way. In that way, we will never have chance to > put kernel above 64TB even from 5-level kernel to jump to 5-level > kernel. > It sounds like you have no intent of doing that anyway? Now, that is something one could use an xloadflag for, as I previously stated: "this kernel supports being entered in 5-level mode." -hpa