Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4688401imm; Mon, 17 Sep 2018 19:49:19 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZWC+iXVItvnWYAleSbwLGMAg8MlMn60nVkAOKBaA7qKjDrFZTr1ycoTipO4kisJTuRgQqY X-Received: by 2002:a17:902:b81:: with SMTP id 1-v6mr27569632plr.319.1537238959751; Mon, 17 Sep 2018 19:49:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537238959; cv=none; d=google.com; s=arc-20160816; b=qLl6lBiV9uH7Zh73Ldh5ZdIS1vcOYNxlD+C863HzkNy+r5sgjNPUDjBzF0DRf5ap2I sWmcBs4JvHt9sjnfzeA4U+/w8kXvpSxgf/KflbM5l831KtUx6Y2JeH+Zbtbtnatu7exK BSeTMSzJZV/q6YXea9OrDy7x2ERW7JEzlQupgAyLUcjPiji2PcpFVm0ngK1wWVHsi/Bx YbeTRxiHROp+tms7QES2PurX8ufL0RX48xJnSCzU8Nw6bGc85FQMWiVSHVkNSfdQfzGM Wy1Qkl3aZ0pRrGsBCdDEjSiLIOGwUqR+JyYXhQdI+RXMVV6MJvF7Bj5ZFSjZ/RiT0909 9nXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=IcKLZ6KoqYQIOxfKJRP5xxkT8oA5lxsKHjNNstVxkAQ=; b=0V0F7qaPRaJZjU/3v9xZNJW+T5RTpwIg/NVUd52OggPzywnAo6uZnpc7384eCDP7pb 2UtNEzESnTVd9yPjAqOuJB89plTnzCeh3/xXx7EO4BHhZxxUJQEX+WXo9NYdMsE6/irQ L6FB+Rcy0pY0Lj7sQ0TElW/xezUq1oH8iVNyHlWSm5RLB0LSLRjPsMsMWK2qYk0HVfjP ikFTzkQydDcZsL4ZpsJrDju3PVu6bqEgJbJEQlt6gkWM9Sa1HEFgtM7IgHL2gw1jc/uF pAr2UpuUlrPH+cd99FRAJf/P6qw61dafVSX++qBJk9VqjuxPmqTKE5dK73ohxYLGIX05 wVQg== 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 q23-v6si15574808pgq.483.2018.09.17.19.49.04; Mon, 17 Sep 2018 19:49:19 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727471AbeIRITM (ORCPT + 99 others); Tue, 18 Sep 2018 04:19:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34376 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725787AbeIRITM (ORCPT ); Tue, 18 Sep 2018 04:19:12 -0400 Received: from smtp.corp.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 5B058356D4; Tue, 18 Sep 2018 02:48:50 +0000 (UTC) Received: from localhost.localdomain.com (ovpn-12-52.pek2.redhat.com [10.72.12.52]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4E71030912F4; Tue, 18 Sep 2018 02:48:41 +0000 (UTC) From: Lianbo Jiang To: linux-kernel@vger.kernel.org Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, akpm@linux-foundation.org, dyoung@redhat.com Subject: [PATCH 0/2] x86/kexec_file: add reserved e820 ranges to the kdump kernel e820 table Date: Tue, 18 Sep 2018 10:48:35 +0800 Message-Id: <20180918024837.17710-1-lijiang@redhat.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.26 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Tue, 18 Sep 2018 02:48:50 +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, we have added this in kexec-tools code. One reason is PCI mmconf (extended mode) requires reserved region otherwise it falls back to legacy mode. Furthermore, when AMD SME kdump support, it needs to map dmi table area as unencrypted. For normal boot these ranges sit in e820 reserved ranges thus the early ioremap code naturally map them as unencrypted. So if we have same e820 reserve setup in kdump kernel then it will just work like normal kernel. Kdump use walk_iomem_res_desc to iterate resources then add matched desc to e820 table for the kdump kernel. But IORES_DESC_NONE resource type includes several different e820 types, we need add exact e820 type to the kdump kernel e820 table thus need an extra checking in memmap_entry_callback to match the e820 type and resource name. NOTE: Before verifying this patches, you need to merge the following patch, which uses to fix an upstream bug. For more information, you can refer to the link below. https://lore.kernel.org/patchwork/patch/986979/ Lianbo Jiang (2): x86/kexec_file: add e820 entry in case e820 type string matches to io resource name x86/kexec_file: add reserved e820 ranges to 2nd kernel e820 table arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/crash.c | 12 +++++++++++- arch/x86/kernel/e820.c | 2 +- kernel/resource.c | 1 + 4 files changed, 15 insertions(+), 2 deletions(-) -- 2.17.1