Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2714866imu; Tue, 6 Nov 2018 21:02:22 -0800 (PST) X-Google-Smtp-Source: AJdET5fsgeZh/A7qtYsAW/WW8pvzbQVaqLhi1SQphEhkLqYx0xtNk23t0k8us8qpGtCuyWC4SwID X-Received: by 2002:a63:2bc9:: with SMTP id r192mr438727pgr.172.1541566942741; Tue, 06 Nov 2018 21:02:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541566942; cv=none; d=google.com; s=arc-20160816; b=jbzaIsj3cm4KXUOyU/zG4JeNtNvM744ex9vsWwY8mvQgJKhDzEpec2Zf/4VT3v+OuV x3wxPnSaJYt/BPmK43Gc8cJMx5mFJuV1aZ3jXm8PFfmrlmE5oLqycpbSZvSLyzrWJkuA srSHLNDYKYkUu5pcNWygIsKWlq8ys5iuiuoHVEbfgcsZoq9hT4YD1GlRkJy4svcX+Amy 2LJUCoXyTrDqqhfi+Sg25a5Ldz411s2OVXv9gAnE8ous/Spjg02GgU0BlrlCufTVeTGu pqqd2UWcsy2FjI41L6M5fWoHINf84cwq7sWNJBdL610GKJgf1qqMDuGmdDJOEdxYDiEW bnYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=wJu1vNyJ2TKFDrPR8e4AdCNgqjNnjJCjB8deii9dm44=; b=WqdlC2cNzEC5PQyQZu7DfaN/qeSCORQ/135Wlgg6pNX3WKDBSIQp3PH9ciGF9oUe4J QgX+J7RBEGL4C89LR+Dn9DyZ17ER8QHHhVt5hF5OqIH4C4OaNrCwO7BiMoLwmgmooTYG 9re8avMinMU7GSqM2Ozc5T/fmnEZz058vkQ7NYmh0Jc5a99kWuks9Z/isk15OYrs6H1B bAAqkxCtesnq27JTzh63GvI7JGCxEdcBR5viFTEBbo8+Rz7Hzwc5ql6ODDiNhw8rpUJ4 uxbI3jkkwtIjH5GhIWG8XKZIetgnSQzWFOECWhXIs4OVvFRcq3HAJ6j/qfEQ/wyfnFmg vSUw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b2-v6si28365470pgg.412.2018.11.06.21.02.07; Tue, 06 Nov 2018 21:02:22 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389070AbeKGO3l (ORCPT + 99 others); Wed, 7 Nov 2018 09:29:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40376 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388994AbeKGO3l (ORCPT ); Wed, 7 Nov 2018 09:29:41 -0500 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C6E4D308FB99; Wed, 7 Nov 2018 05:00:57 +0000 (UTC) Received: from localhost.localdomain.com (ovpn-12-97.pek2.redhat.com [10.72.12.97]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1809D68D27; Wed, 7 Nov 2018 05:00:49 +0000 (UTC) From: Lianbo Jiang To: linux-kernel@vger.kernel.org Cc: kexec@lists.infradead.org, x86@kernel.org, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, akpm@linux-foundation.org, dyoung@redhat.com, bhe@redhat.com Subject: [PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table Date: Wed, 7 Nov 2018 13:00:19 +0800 Message-Id: <20181107050019.6663-3-lijiang@redhat.com> In-Reply-To: <20181107050019.6663-1-lijiang@redhat.com> References: <20181107050019.6663-1-lijiang@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Wed, 07 Nov 2018 05:00:57 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org E820 reserved ranges is useful in kdump kernel, it has been added in kexec-tools code. One reason is PCI mmconf (extended mode) requires reserved region otherwise it falls back to legacy mode, and also outputs the following kernel log. Example: ...... [ 19.798354] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 19.800653] [Firmware Info]: PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] not reserved in ACPI motherboard resources [ 19.800995] PCI: not using MMCONFIG ...... The correct kernel log is like this: ...... [ 0.082649] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 0.083610] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820 ...... Furthermore, when AMD SME kdump support, it needs to map dmi table area as decrypted. For normal boot, these ranges sit in e820 reserved ranges, thus the early ioremap code naturally map them as decrypted. If it also has same e820 reserve setup in kdump kernel then it will just work like normal kernel. Suggested-by: Dave Young Signed-off-by: Lianbo Jiang --- arch/x86/kernel/crash.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c index ae724a6e0a5f..d3167125800e 100644 --- a/arch/x86/kernel/crash.c +++ b/arch/x86/kernel/crash.c @@ -384,6 +384,10 @@ int crash_setup_memmap_entries(struct kimage *image, struct boot_params *params) walk_iomem_res_desc(IORES_DESC_ACPI_NV_STORAGE, flags, 0, -1, &cmd, memmap_entry_callback); + cmd.type = E820_TYPE_RESERVED; + walk_iomem_res_desc(IORES_DESC_NONE, 0, 0, -1, &cmd, + memmap_entry_callback); + /* Add crashk_low_res region */ if (crashk_low_res.end) { ei.addr = crashk_low_res.start; -- 2.17.1