From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751927AbeEGCso (ORCPT ); Sun, 6 May 2018 22:48:44 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:52806 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751852AbeEGCsm (ORCPT ); Sun, 6 May 2018 22:48:42 -0400 Date: Mon, 7 May 2018 10:48:33 +0800 From: Dave Young To: akpm@linux-foundation.org Cc: bhe@redhat.com, yinghai@kernel.org, akpm@linux-foundation.org, vgoyal@redhat.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] kdump/x86: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM Message-ID: <20180507024833.GA3895@dhcp-128-65.nay.redhat.com> References: <20180427090045.532014306@redhat.com> <20180427091410.GA25338@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180427091410.GA25338@dhcp-128-65.nay.redhat.com> User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/27/18 at 05:14pm, Dave Young wrote: > Hi, > > This is a resend of below patches: > http://lists.infradead.org/pipermail/kexec/2017-October/019569.html > > I dropped the original patch 1 since Baoquan is not happy with it. > For patch 2 (the 1st patch in this series), there is some improvement > comment from Baoquan to create some generic memblock iteration function. > But nobody has time to work on it for the time being. According to > offline discussion with him. That can be done in the future if someone > is interested. We can go with the current kdump only fixes. > > Other than above, the patches are just same. Hi Andrew, do you have concerns about the patches? It has been used for long time in Red Hat kernel, since people do not object them, could you pick them if no other concerns? Thanks Dave