From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lixom.net (lixom.net [66.141.50.11]) by ozlabs.org (Postfix) with ESMTP id D2AFF67B36 for ; Fri, 24 Mar 2006 07:13:32 +1100 (EST) Date: Thu, 23 Mar 2006 14:12:58 -0600 To: Olof Johansson Subject: Re: [PATCH] kdump: Fix for machine checkstop on DMA fault Message-ID: <20060323201258.GA5538@pb15.lixom.net> References: <44222462.2030103@us.ibm.com> <20060323053854.GA17693@pb15.lixom.net> <200603231706.35508.michael@ellerman.id.au> <20060323061904.GA22439@pb15.lixom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20060323061904.GA22439@pb15.lixom.net> From: Olof Johansson Cc: Milton Miller , Michael Ellerman , linuxppc-dev@ozlabs.org, Paul Mackerras , Olaf Hering , ellerman@au1.ibm.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Mar 23, 2006 at 12:19:04AM -0600, Olof Johansson wrote: > The crash kernel needs to be even more careful, and instead read out > the entries that are mapped and reserve them. This would require a bit > more plumbing since there's no way to read an entry right now, but it'd > remove that hole. Actually, what's probably easier is to allocate some entries when the purgatory is set up, and make the crash kernel only use those by modifying the device tree accordingly. Sort of how regular memory is handled right now. That'd be a cleaner solution with less changes needed. The trick will be to get a decent size contiguous allocation, but the same applies for the memory reserve. -Olof