From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756074Ab3A2CNG (ORCPT ); Mon, 28 Jan 2013 21:13:06 -0500 Received: from terminus.zytor.com ([198.137.202.10]:48532 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756017Ab3A2CNE (ORCPT ); Mon, 28 Jan 2013 21:13:04 -0500 Message-ID: <51072FEF.50000@zytor.com> Date: Mon, 28 Jan 2013 18:11:59 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yinghai Lu CC: Thomas Renninger , x86@kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org, vgoyal@redhat.com, horms@verge.net.au Subject: Re: [PATCH 2/2] x86 e820: Introduce memmap=resetusablemap for kdump usage References: <1358868049-19884-1-git-send-email-trenn@suse.de> <6950516.1uefDuthAH@hammer82.arch.suse.de> <510721C6.6080705@zytor.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/28/2013 06:10 PM, Yinghai Lu wrote: > > kexec-tools will change that to E820_KDUMP_RESERVED (or other good name). > > We only need to update kernel to get old max_pfn by > checking E820_KDUMP_RESERVED. > OK, I have asked this before, but I still have not gotten any acceptable answer: Why do we still have max_*_pfn at all? Shouldn't it all be based on memblocks by now? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.