Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp6957817pxb; Wed, 17 Feb 2021 19:36:39 -0800 (PST) X-Google-Smtp-Source: ABdhPJyM2MkrYjYnXaa2ONgfYkKwMvcDNQnzx8TFss7foeJV4OzfE5DoMPg4ikAhFP6/VrWtjukg X-Received: by 2002:a05:6402:100b:: with SMTP id c11mr1893859edu.193.1613619399702; Wed, 17 Feb 2021 19:36:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613619399; cv=none; d=google.com; s=arc-20160816; b=C+ktM06xAKXT/YDYiA1SP8lH3TBlWZARXD5AzeYhCHzvuEi+G9TB/AIdiQ3Y8HzDuS 8TuLnjsq3nW3Pah0tXBt5ub0L7+wwNTafIktxiaRazLu+hp6eKrfDhP0UFm7ZvUcX51s DdZo0p/DSlUqcCJ/DNsFZini655GateB8lxz/ASAA20mLtcPK+C0rUhfikYgjhM1gahv EHuw8U+ElL0YZupREkHePj3T+jdIRhjitFNkqanP2VP6uHFEs8sh4djOEA9akI3sFX/Q IVW7YyNQG8DTSWSx+hyO0bhy0Tkhtg7CyzzdXhNqWI9Sy+d2DWdZ7u3/lFsrhIma0rx0 8cYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=d9YnNO3MbpPkDoXl8YrBEEv+qOhDiCyZjDCW4nbXIvQ=; b=dvwiafcTLgK1ccWMKIOImGcxlPlq/rgqhM2VL6+3NEYzbMz8r4v8LzaNc18cXgAPRi EhDRMmeCEpNlBUpjxYm0jinZRdv+ECxYABDQaI0CsKWn4DUmBOFNj4Mgb0FOuqVGgTQi acMksznzRvKy4MUVkD98I11O/RirsDFqfSE5oR2/oxbShbunHn54byJZlNcCyDRjdeli VJg/NCla7/0eK7QoncE0P8URT2MQ38PGuFJz/johD1FjAiXNq/eFiLOmhcJOMgsUL6W9 /8YkG6MvKboZHPhX9de674/XgKuZr0+FrCriV4cZYzdWugOohw/AXov9B9emeIA0dZDW tBMA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=CFsd87Gu; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i20si2782736edg.156.2021.02.17.19.36.02; Wed, 17 Feb 2021 19:36:39 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=CFsd87Gu; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229889AbhBRDfd (ORCPT + 99 others); Wed, 17 Feb 2021 22:35:33 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:29628 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229885AbhBRDfc (ORCPT ); Wed, 17 Feb 2021 22:35:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1613619246; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=d9YnNO3MbpPkDoXl8YrBEEv+qOhDiCyZjDCW4nbXIvQ=; b=CFsd87GuAsC9yUTBC9Jmdu8+/tk2VV834Hh70YWJOyeDYaqTECMhwEdRCFId3W+ci8+5rG XtrlAomsaLoZBKgGcIPPuHeOFJZ1ZekkiSJIWo8OGcvOFHh9hcvakoMKh1nwtOxUzoioAi VN8UW6xEMRAhA+tWkwVGGMCbdnYpH4I= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-447-aOSWgkEAPimUDD-8gCggqA-1; Wed, 17 Feb 2021 22:34:02 -0500 X-MC-Unique: aOSWgkEAPimUDD-8gCggqA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8068710066F1; Thu, 18 Feb 2021 03:33:59 +0000 (UTC) Received: from localhost (ovpn-12-112.pek2.redhat.com [10.72.12.112]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 84C09100164C; Thu, 18 Feb 2021 03:33:55 +0000 (UTC) Date: Thu, 18 Feb 2021 11:33:52 +0800 From: Baoquan He To: Chen Zhou Cc: mingo@redhat.com, tglx@linutronix.de, rppt@kernel.org, dyoung@redhat.com, catalin.marinas@arm.com, will@kernel.org, nsaenzjulienne@suse.de, corbet@lwn.net, John.P.donnelly@oracle.com, prabhakar.pkin@gmail.com, horms@verge.net.au, robh+dt@kernel.org, arnd@arndb.de, james.morse@arm.com, xiexiuqi@huawei.com, guohanjun@huawei.com, huawei.libin@huawei.com, wangkefeng.wang@huawei.com, linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v14 02/11] x86: kdump: make the lower bound of crash kernel reservation consistent Message-ID: <20210218033233.GF2871@MiWiFi-R3L-srv> References: <20210130071025.65258-1-chenzhou10@huawei.com> <20210130071025.65258-3-chenzhou10@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210130071025.65258-3-chenzhou10@huawei.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/30/21 at 03:10pm, Chen Zhou wrote: > The lower bounds of crash kernel reservation and crash kernel low > reservation are different, use the consistent value CRASH_ALIGN. > > Suggested-by: Dave Young > Signed-off-by: Chen Zhou > Tested-by: John Donnelly > --- > arch/x86/kernel/setup.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c > index da769845597d..27470479e4a3 100644 > --- a/arch/x86/kernel/setup.c > +++ b/arch/x86/kernel/setup.c > @@ -439,7 +439,8 @@ static int __init reserve_crashkernel_low(void) > return 0; > } > > - low_base = memblock_phys_alloc_range(low_size, CRASH_ALIGN, 0, CRASH_ADDR_LOW_MAX); > + low_base = memblock_phys_alloc_range(low_size, CRASH_ALIGN, CRASH_ALIGN, > + CRASH_ADDR_LOW_MAX); Acked-by: Baoquan He > if (!low_base) { > pr_err("Cannot reserve %ldMB crashkernel low memory, please try smaller size.\n", > (unsigned long)(low_size >> 20)); > -- > 2.20.1 >