From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.skyhub.de ([5.9.137.197]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gp9vZ-0005Bk-NE for kexec@lists.infradead.org; Thu, 31 Jan 2019 10:50:41 +0000 Date: Thu, 31 Jan 2019 11:50:19 +0100 From: Borislav Petkov Subject: Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr Message-ID: <20190131105019.GB6749@zn.tnic> References: <1548047768-7656-1-git-send-email-kernelfans@gmail.com> <20190125103924.GB27998@zn.tnic> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Pingfan Liu Cc: x86@kernel.org, Baoquan He , Dave Young , Randy Dunlap , kexec@lists.infradead.org, LKML , Mike Rapoport , Andrew Morton , Yinghai Lu , vgoyal@redhat.com On Tue, Jan 29, 2019 at 01:51:45PM +0800, Pingfan Liu wrote: > Sorry, can not catch up with you. Do you suggestion > memblock_find_in_range(0, kernel_start) and > memblock_find_in_range(kernel_end, mem_end)? But the memory is > truncated into fraction by many component which call > memblock_reserve(), besides kernel. extract_kernel() selects the physical address where the place the kernel. You can use that physical address to figure out where to allocate the crash kernel range. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec