Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2002369ybt; Thu, 2 Jul 2020 20:58:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwbogL/U3emq7Ybw27LmTe6RszizG+DDVNdzWxHgCEZTwp7YdRpr037io4RsoO/Iq+7Drul X-Received: by 2002:a05:6402:1c0f:: with SMTP id ck15mr36783267edb.155.1593748679967; Thu, 02 Jul 2020 20:57:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593748679; cv=none; d=google.com; s=arc-20160816; b=lUJ0PlpvUgYbFugy+LFteMF68bT8JIYGdHILgsfXDZZuCm7cel4A6YnnvGJzsdzifJ k+qootyzmH6iusmie8WoJrDahAmDaaosc2XCG9w9xeWbPr+3swCZVEXH5GUjQhK0bBdE BcwR7q+jilKCFhHh0vTTNAJqxKK+DGmxgC5Fk30sxpFkuDdp4WrJ7eq30J4if/OJLlbS tyPxDqU0gQbHH9Me6v5QW9/1aytkrYbSV04008ikm7zUQO8NLFg9G9bO60L8WK4xi7Lw 7XTSclnOGgSRCFzRcy0U+ni1xn72Dzdj7+B/2fugwx6VYTozkb2MmNXMONnAHW7bO1xy qIWA== 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:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=Bdybb7AhtGKBz3gLa+lhwb6WBog+t2xJBYT1OThL5xQ=; b=Ybir0OvVEc6si4lajFOQuGyhp3fqeNz9jnJ9FcsOmtjVcnUW3y825RZ9wjeGTyJQbu 12DXE8CZDwLLKesqVPeDo3rh/z5S6Q69z7SLbJ3BK70tXra2UHO7UhraJlkYZ72nzvcW BJnxdhU0zkRp6f5CwdbXawMhwBzzqGWhuC8xgokXHhUxaZl1kIzJuBSKdv+Tb/x7AVz0 5aYZ2W7H/IWIsjhoVUNt1pXVMM3fVhbvsGJVZzkgPeSgDCw2/er3SBvjvJq9HNRk+70v HdlJ1XecNeacvk+CNfTLw5md4bctYZ5xhCnnsUJlzz5Y5sxCJ1zzJVsjoAIDniyq54VP dpxw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ss22si7817567ejb.530.2020.07.02.20.57.37; Thu, 02 Jul 2020 20:57:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726129AbgGCDyT (ORCPT + 99 others); Thu, 2 Jul 2020 23:54:19 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:7364 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725915AbgGCDyS (ORCPT ); Thu, 2 Jul 2020 23:54:18 -0400 Received: from DGGEMS403-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id DF5AA8E37ECDC634B836; Fri, 3 Jul 2020 11:53:59 +0800 (CST) Received: from localhost.localdomain.localdomain (10.175.113.25) by DGGEMS403-HUB.china.huawei.com (10.3.19.203) with Microsoft SMTP Server id 14.3.487.0; Fri, 3 Jul 2020 11:53:49 +0800 From: Chen Zhou To: , , , , , , , , , , , , , , CC: , , , , , , , Subject: [PATCH v10 2/5] arm64: kdump: reserve crashkenel above 4G for crash dump kernel Date: Fri, 3 Jul 2020 11:58:13 +0800 Message-ID: <20200703035816.31289-3-chenzhou10@huawei.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200703035816.31289-1-chenzhou10@huawei.com> References: <20200703035816.31289-1-chenzhou10@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.175.113.25] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Crashkernel=X tries to reserve memory for the crash dump kernel under 4G. If crashkernel=X,low is specified simultaneously, reserve spcified size low memory for crash kdump kernel devices firstly and then reserve memory above 4G. Suggested by James, just introduced crashkernel=X,low to arm64. As memtioned above, if crashkernel=X,low is specified simultaneously, reserve spcified size low memory for crash kdump kernel devices firstly and then reserve memory above 4G, which is much simpler. Signed-off-by: Chen Zhou Tested-by: John Donnelly Tested-by: Prabhakar Kushwaha --- arch/arm64/kernel/setup.c | 8 +++++++- arch/arm64/mm/init.c | 31 +++++++++++++++++++++++++++++-- 2 files changed, 36 insertions(+), 3 deletions(-) diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c index 93b3844cf442..4dc51a2ac012 100644 --- a/arch/arm64/kernel/setup.c +++ b/arch/arm64/kernel/setup.c @@ -238,7 +238,13 @@ static void __init request_standard_resources(void) kernel_data.end <= res->end) request_resource(res, &kernel_data); #ifdef CONFIG_KEXEC_CORE - /* Userspace will find "Crash kernel" region in /proc/iomem. */ + /* + * Userspace will find "Crash kernel" region in /proc/iomem. + * Note: the low region is renamed as Crash kernel (low). + */ + if (crashk_low_res.end && crashk_low_res.start >= res->start && + crashk_low_res.end <= res->end) + request_resource(res, &crashk_low_res); if (crashk_res.end && crashk_res.start >= res->start && crashk_res.end <= res->end) request_resource(res, &crashk_res); diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c index 1e93cfc7c47a..ce7ced85f5fb 100644 --- a/arch/arm64/mm/init.c +++ b/arch/arm64/mm/init.c @@ -81,6 +81,7 @@ static void __init reserve_crashkernel(void) { unsigned long long crash_base, crash_size; int ret; + phys_addr_t crash_max = arm64_dma32_phys_limit; ret = parse_crashkernel(boot_command_line, memblock_phys_mem_size(), &crash_size, &crash_base); @@ -88,12 +89,38 @@ static void __init reserve_crashkernel(void) if (ret || !crash_size) return; + ret = reserve_crashkernel_low(); + if (!ret && crashk_low_res.end) { + /* + * If crashkernel=X,low specified, there may be two regions, + * we need to make some changes as follows: + * + * 1. rename the low region as "Crash kernel (low)" + * In order to distinct from the high region and make no effect + * to the use of existing kexec-tools, rename the low region as + * "Crash kernel (low)". + * + * 2. change the upper bound for crash memory + * Set MEMBLOCK_ALLOC_ACCESSIBLE upper bound for crash memory. + * + * 3. mark the low region as "nomap" + * The low region is intended to be used for crash dump kernel + * devices, just mark the low region as "nomap" simply. + */ + const char *rename = "Crash kernel (low)"; + + crashk_low_res.name = rename; + crash_max = MEMBLOCK_ALLOC_ACCESSIBLE; + memblock_mark_nomap(crashk_low_res.start, + resource_size(&crashk_low_res)); + } + crash_size = PAGE_ALIGN(crash_size); if (crash_base == 0) { /* Current arm64 boot protocol requires 2MB alignment */ - crash_base = memblock_find_in_range(0, arm64_dma32_phys_limit, - crash_size, SZ_2M); + crash_base = memblock_find_in_range(0, crash_max, crash_size, + SZ_2M); if (crash_base == 0) { pr_warn("cannot allocate crashkernel (size:0x%llx)\n", crash_size); -- 2.20.1