Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp27015074rwd; Mon, 3 Jul 2023 19:22:05 -0700 (PDT) X-Google-Smtp-Source: APBJJlGJ/kwN26QC7Gf/X9wbUFSZ0MCVupZRZ9zBHqtWedAMYeLVwlXZAAdOi3MrvkPBVwFWVHxs X-Received: by 2002:a05:6870:b68f:b0:1b0:449e:cff9 with SMTP id cy15-20020a056870b68f00b001b0449ecff9mr10848941oab.57.1688437324798; Mon, 03 Jul 2023 19:22:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688437324; cv=none; d=google.com; s=arc-20160816; b=m4kjdRBqF6GcoNXuNZQcThwH3l57/IH93N84vBIkP+42SbQrXGsYH8is6lX1cYW8rH 2gqb6PUXRSRQYhbs5hs6dKDY0vIVIxxfMKYjt/yAyxS4Peoi5IAP/clES8iIsfbaBgnz 61V5NHVZpptl5HA4M/rwHAveoLR+ZQFEy23oYR4YVOUP8r2YQTz4aS8ygPItuSBMpYEv Q3jATAp/0NvL5i/x44D5rJoQxWZ4ge8PGA/lPWRP+/zlHUq8bzFuCJ3VnoyUZioTm1hZ A49eaIbWXhlFc/v12+OMBQQ79w7ksi8KQf/t5bk13ILSCdDLGZiSUWAC89C59xwv6Lgj kByw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=TQQR/63S81FCx6mPVXjTBcSfGMPVTLfqH529zoemobM=; fh=vw9u85W9WqbGbhgYgKqNJ9lNaY7+J+Ml+4iNcEZdfo4=; b=ZJQ+IzswEJZzCz1kJfc3/y0bW5nPcx0F9UF1wWGdvaGezgIpB2QnLQpzwAF5bBGi4v I5k0h7rfuPfMaj5M86uaaXZl4YRBt/xC73hEmixAE7mWXyHLOmB3GM/+Vjn3xFuoGE5z 8/x9IdYrdGQS1g4Yg8PRdrJm470dMuCzFzIO8pMnW6yCYV05ZdF5t+YTf7K2+0ZzfEA6 KXW8VxH5o4xsMAXTZaFqYv7JhuaEawggqru+7ag+tyIHQ9qad2e3eydxcxW5Db+TwVQR DbfnvrFm8q1W3hZdaMp3pEOMzEQktTTWZLY96b0AYoKB3rzRLavXtHQdUPfI3QIHsZDe ko2w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hg4-20020a17090b300400b00262dc058680si17821852pjb.123.2023.07.03.19.21.48; Mon, 03 Jul 2023 19:22:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231462AbjGDCSM (ORCPT + 99 others); Mon, 3 Jul 2023 22:18:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58832 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229505AbjGDCSL (ORCPT ); Mon, 3 Jul 2023 22:18:11 -0400 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 24C69136; Mon, 3 Jul 2023 19:18:09 -0700 (PDT) Received: from dggpemm500016.china.huawei.com (unknown [172.30.72.54]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4Qw5zV0z3YzqSMj; Tue, 4 Jul 2023 10:17:42 +0800 (CST) Received: from [10.67.108.26] (10.67.108.26) by dggpemm500016.china.huawei.com (7.185.36.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Tue, 4 Jul 2023 10:18:02 +0800 Message-ID: <6f4c80ba-ec61-2ce8-3034-08162f0ee9fd@huawei.com> Date: Tue, 4 Jul 2023 10:18:01 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCH -next v6 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Content-Language: en-US To: Baoquan He CC: , , , , , , , , , , , , , , References: <20230701171138.1491206-1-chenjiahao16@huawei.com> <20230701171138.1491206-2-chenjiahao16@huawei.com> From: "chenjiahao (C)" In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.108.26] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To dggpemm500016.china.huawei.com (7.185.36.25) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023/7/2 12:12, Baoquan He wrote: > On 07/01/23 at 05:11pm, Chen Jiahao wrote: >> On riscv, the current crash kernel allocation logic is trying to >> allocate within 32bit addressible memory region by default, if >> failed, try to allocate without 4G restriction. >> >> In need of saving DMA zone memory while allocating a relatively large >> crash kernel region, allocating the reserved memory top down in >> high memory, without overlapping the DMA zone, is a mature solution. >> Here introduce the parameter option crashkernel=X,[high,low]. >> >> One can reserve the crash kernel from high memory above DMA zone range >> by explicitly passing "crashkernel=X,high"; or reserve a memory range >> below 4G with "crashkernel=X,low". >> >> Signed-off-by: Chen Jiahao >> Acked-by: Guo Ren >> --- >> arch/riscv/kernel/setup.c | 5 +++ >> arch/riscv/mm/init.c | 84 +++++++++++++++++++++++++++++++++++---- >> 2 files changed, 82 insertions(+), 7 deletions(-) >> >> diff --git a/arch/riscv/kernel/setup.c b/arch/riscv/kernel/setup.c >> index 971fe776e2f8..376f5d49ce85 100644 >> --- a/arch/riscv/kernel/setup.c >> +++ b/arch/riscv/kernel/setup.c >> @@ -178,6 +178,11 @@ static void __init init_resources(void) >> if (ret < 0) >> goto error; >> } >> + if (crashk_low_res.start != crashk_low_res.end) { >> + ret = add_resource(&iomem_resource, &crashk_low_res); >> + if (ret < 0) >> + goto error; >> + } >> #endif >> >> #ifdef CONFIG_CRASH_DUMP >> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c >> index 4b95d8999120..eeb31c2cc843 100644 >> --- a/arch/riscv/mm/init.c >> +++ b/arch/riscv/mm/init.c >> @@ -1298,6 +1298,28 @@ static inline void setup_vm_final(void) >> } >> #endif /* CONFIG_MMU */ >> >> +/* Reserve 128M low memory by default for swiotlb buffer */ >> +#define DEFAULT_CRASH_KERNEL_LOW_SIZE (128UL << 20) >> + >> +static int __init reserve_crashkernel_low(unsigned long long low_size) >> +{ >> + unsigned long long low_base; >> + >> + low_base = memblock_phys_alloc_range(low_size, PMD_SIZE, 0, dma32_phys_limit); >> + if (!low_base) { >> + pr_err("cannot allocate crashkernel low memory (size:0x%llx).\n", low_size); >> + return -ENOMEM; >> + } >> + >> + pr_info("crashkernel low memory reserved: 0x%016llx - 0x%016llx (%lld MB)\n", >> + low_base, low_base + low_size, low_size >> 20); >> + >> + crashk_low_res.start = low_base; >> + crashk_low_res.end = low_base + low_size - 1; >> + >> + return 0; >> +} >> + >> /* >> * reserve_crashkernel() - reserves memory for crash kernel >> * >> @@ -1309,8 +1331,12 @@ static void __init reserve_crashkernel(void) >> { >> unsigned long long crash_base = 0; >> unsigned long long crash_size = 0; >> + unsigned long long crash_low_size = 0; >> unsigned long search_start = memblock_start_of_DRAM(); >> - unsigned long search_end = memblock_end_of_DRAM(); >> + unsigned long search_end = (unsigned long)dma32_phys_limit; >> + char *cmdline = boot_command_line; >> + bool fixed_base = false; >> + bool high = false; >> >> int ret = 0; >> >> @@ -1326,14 +1352,36 @@ static void __init reserve_crashkernel(void) >> return; >> } >> >> - ret = parse_crashkernel(boot_command_line, memblock_phys_mem_size(), >> + ret = parse_crashkernel(cmdline, memblock_phys_mem_size(), >> &crash_size, &crash_base); >> - if (ret || !crash_size) >> + if (ret == -ENOENT) { >> + /* Fallback to crashkernel=X,[high,low] */ >> + ret = parse_crashkernel_high(cmdline, 0, &crash_size, &crash_base); >> + if (ret || !crash_size) >> + return; >> + >> + /* >> + * crashkernel=Y,low is valid only when crashkernel=X,high >> + * is passed. >> + */ >> + ret = parse_crashkernel_low(cmdline, 0, &crash_low_size, &crash_base); >> + if (ret == -ENOENT) >> + crash_low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE; >> + else if (ret) >> + return; >> + >> + search_start = (unsigned long)dma32_phys_limit; >> + search_end = memblock_end_of_DRAM(); >> + high = true; >> + } else if (ret || !crash_size) { >> + /* Invalid argument value specified */ >> return; >> + } >> >> crash_size = PAGE_ALIGN(crash_size); >> >> if (crash_base) { >> + fixed_base = true; >> search_start = crash_base; >> search_end = crash_base + crash_size; >> } >> @@ -1346,17 +1394,39 @@ static void __init reserve_crashkernel(void) >> * swiotlb can work on the crash kernel. >> */ >> crash_base = memblock_phys_alloc_range(crash_size, PMD_SIZE, >> - search_start, >> - min(search_end, (unsigned long) SZ_4G)); >> + search_start, search_end); >> if (crash_base == 0) { >> - /* Try again without restricting region to 32bit addressible memory */ >> + if (fixed_base) { >> + pr_warn("crashkernel: allocating failed with given size@offset\n"); >> + return; >> + } >> + >> + if (high) { >> + /* Fall back to lower 32G reservation */ >> + search_start = memblock_start_of_DRAM(); >> + search_end = (unsigned long)dma32_phys_limit; >> + } else { >> + /* Try again above the region of 32bit addressible memory */ >> + search_start = (unsigned long)dma32_phys_limit; >> + search_end = memblock_end_of_DRAM(); >> + } >> + >> crash_base = memblock_phys_alloc_range(crash_size, PMD_SIZE, >> - search_start, search_end); >> + search_start, search_end); >> if (crash_base == 0) { >> pr_warn("crashkernel: couldn't allocate %lldKB\n", >> crash_size >> 10); >> return; >> } >> + >> + if (!crash_low_size) >> + crash_low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE; > How do you differentiate the case user specifies crashkernel=0M,low > explicitly with the case that user doesn't specify crashkernel=,low, but > only specify crsahkernel=xM,high? I saw you don't have the test case > crashkernel=xM,high crashkernel=0M,low listed in your cover letter. Yes, here is indeed a point not exactly aligned with Arm64 code. But testcases below seem to have the same result with Arm64: crashkernel=512M,high //high=512M, low=128M (default) crashkernel=512M,high crashkernel=0M,low //high=512M, low=0M crashkernel=512M,high crashkernel=256M,low //high=512M, low=256M When the first allocation succeed, it will not fallback into the if (crash_base == 0) case, the allocation result is the same as Arm64, both for explicitly given "crashkernel=0M,low" or not. The problem you mentioned might occurs when the first allocation failed. My logic here is when crashkernel=xM,high is specified, no matter crashkernel=0M,low is explicitly given or not, "high" flag is set. It will fallback to lower 4G allocation, additional lower 4G region with "crash_low_size" will never get reserved. So the results between Arm64 and riscv when crashkernel=,low is specified or not are the same. Is there any problem with my logic, or have I misunderstood your comment above? > >> + } >> + >> + if ((crash_base >= dma32_phys_limit) && crash_low_size && >> + reserve_crashkernel_low(crash_low_size)) { Here, additional lower memory region will not reserve when crashkernel=xM,high is given >> + memblock_phys_free(crash_base, crash_size); >> + return; >> } >> >> pr_info("crashkernel: reserved 0x%016llx - 0x%016llx (%lld MB)\n", >> -- >> 2.34.1 >> Thanks, Jiahao