Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp1243imm; Thu, 30 Aug 2018 07:00:59 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbBdfvhnkrmU/1qtmZHyIzv7NSFAQYP0xAMdCF8a10NhDa1D7KLanIQBELWCqJ9vUbIoZmQ X-Received: by 2002:a63:28c7:: with SMTP id o190-v6mr9916179pgo.84.1535637659702; Thu, 30 Aug 2018 07:00:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535637659; cv=none; d=google.com; s=arc-20160816; b=ECoHFlFP4FvmQBDooVSJX9fMhz/8Azbl8FaXv7pwHFwJxkesij/ixxm9tF7c6aMv7K RHKrr++MT8iZpeN/xi2+a6QAb44enbOR/7nPQZ51yaUnjb5ATzHBrFekKXapjxt/Qdk7 3utdsfmuiHfkW7w9AWQmkkCkZaBaxVe3z65Nc9/3L4k3p5sxbjh9tDxdL+5w7v8kFxIc OqfT2G9iULXZ8AQc2iYuP6XmpvzcQSaTWz4LRsHR7hqqEhTGY1rVljxxG9khRKxW0FMU Io3UxAvKgI6jOdgv/vBF9YuH4U9Bk6Fu6TWQuQ8gByQsI9DzkoPapzNVLxBh7A2rkBLK W4YQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=Opp7/90KgZLyY+6mrs4uBZrkB8MAeRsaRuOg8MZIqwQ=; b=NOhzqi70UUDF/QOkYdjRrSKu1UVt/cKrHgok2PkLxn8dZpLC+BR1uIN++iftPVy7wx bbVlK999j7K6wlg8EAublOZmRUvfBIn5/LCfwtLdbBP1McgvLinlqo+WRm+Aw+xud+y3 dAF4aUW1qX5IbwXTeB0tKYcSyD42kNuE3pCQ66jgNAb9ESFwy2bhesyTa5akzbOxIUlV IYizDQyMCDDhfQn0KQcNhfP5x9RmSMtTBIzUQ4egl0Rja/GLObncFmCx12CEMYRSx5Re iPh86mF+OQ59TaBQhSlOJpF+Ta6Vf/Gjg+4GrrcyVTfJb0rcbaVEtFWKsWp1GIVGXfLF t6dw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b="NCCd/sgd"; 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 b39-v6si7262528plb.484.2018.08.30.07.00.42; Thu, 30 Aug 2018 07:00:59 -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; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b="NCCd/sgd"; 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 S1729046AbeH3SBS (ORCPT + 99 others); Thu, 30 Aug 2018 14:01:18 -0400 Received: from mail-pf1-f195.google.com ([209.85.210.195]:35491 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728273AbeH3SBS (ORCPT ); Thu, 30 Aug 2018 14:01:18 -0400 Received: by mail-pf1-f195.google.com with SMTP id p12-v6so3935316pfh.2 for ; Thu, 30 Aug 2018 06:59:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shutemov-name.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Opp7/90KgZLyY+6mrs4uBZrkB8MAeRsaRuOg8MZIqwQ=; b=NCCd/sgdULlh0dXy3t3REW2/kPqSugZr7dXRGjL0QyoxO98IDuFLESfG7IgdiVEVWl sjGdGwrZ511GZgPtBFEvFAI3EbRd1MPlBEBsRGqEVrnurLFWpcIDiLu2CEM9DC9KKe7t DXtQU01m3mQuWXwZ3M/ySwV8CjVfX1J2hsgASMSbrbIsVAXxZwgwJwnV6IkmaJxobfOl l3OLpR3GgoSLI5GNKcdMcCiUhWUoD0SPEuuk2goinJn3NTnr30YmO7H6wQCk5Xlmf8et /qxSIdBpDs2jshmbkhrgi/kkdwV5LYCpdMEwrBJ46y1KKWSrfBd0umE2qkHq8XDQI9Un w5Hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Opp7/90KgZLyY+6mrs4uBZrkB8MAeRsaRuOg8MZIqwQ=; b=Mh5XluCT0dPNZe5j6pSvSHEY4H+pxrVV5MHkhB5hrMxRJKvZPFcXYYKYkHLd/8rxbG zSUNVi1ZiLBvmPUJl84CsvE8VkWcqz3ZZsTSYS4qR3J1es6NBfI86zqcgosfmgxt2k2H Q1vGO7MK0JaraQixIxkDCobCSsTkpPi0YiRQbopKRq9Jv5tAGR97P1/50RNCiG468nLZ 6ikP6DFltGeLK+PtAsqeziAjYJVHggcSa/J/adKxFJlWd3YAgPgRvSji00fMw03pBO1W 4CqhlGlK6yZNO3vAaFX5zTGLYhp+UVvkbseDQ2Hy/pw3bN3WyWcPgYWGCMTskWmEBfyv SXpg== X-Gm-Message-State: APzg51AqhNc9W3hh9LWAFBCUgiVZVQz5K3tp38TFIxINKAtUxuxUhygN WEqUKHOvpBYSY5II2dqKTFaMQQ== X-Received: by 2002:a62:1bc2:: with SMTP id b185-v6mr10781246pfb.170.1535637541761; Thu, 30 Aug 2018 06:59:01 -0700 (PDT) Received: from kshutemo-mobl1.localdomain ([134.134.139.83]) by smtp.gmail.com with ESMTPSA id v7-v6sm11739585pgh.57.2018.08.30.06.59.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Aug 2018 06:59:00 -0700 (PDT) Received: by kshutemo-mobl1.localdomain (Postfix, from userid 1000) id 222EE3001A3; Thu, 30 Aug 2018 16:58:56 +0300 (+03) Date: Thu, 30 Aug 2018 16:58:56 +0300 From: "Kirill A. Shutemov" To: Baoquan He Cc: tglx@linutronix.de, mingo@kernel.org, hpa@zytor.com, kirill.shutemov@linux.intel.com, x86@kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org Subject: Re: [PATCH 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel Message-ID: <20180830135855.rylamc7mx2ur3tab@kshutemo-mobl1> References: <20180829141624.13985-1-bhe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180829141624.13985-1-bhe@redhat.com> User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 29, 2018 at 10:16:21PM +0800, Baoquan He wrote: > This was suggested by Kirill several months ago, I worked out several > patches to fix, then interrupted by other issues. So sort them out > now and post for reviewing. Thanks for doing this. > The current upstream kernel supports 5-level paging mode and supports > dynamically choosing paging mode during bootup according to kernel > image, hardware and kernel parameter setting. This flexibility brings > several issues for kexec/kdump: > 1) > Switching between paging modes, requires changes into target kernel. > It means you cannot kexec() 4-level paging kernel from 5-level paging > kernel if 4-level paging kernel doesn't include changes. > > 2) > Switching from 5-level paging to 4-level paging kernel would fail, if > kexec() put kernel image above 64TiB of memory. I'm not entirely sure that 64TiB is the limit here. Technically, 4-level paging allows to address 256TiB in 1-to-1 mapping. We just don't have machines with that wide physical address space (which don't support 5-level paging too). What is your reasoning about 64TiB limit? -- Kirill A. Shutemov