From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 08CC02C009C for ; Thu, 16 Jan 2014 12:03:07 +1100 (EST) Message-ID: <1389834172.6933.99.camel@pasglop> Subject: Re: powerpc/powernv: Call OPAL sync before kexec'ing From: Benjamin Herrenschmidt To: Michael Ellerman Date: Thu, 16 Jan 2014 12:02:52 +1100 In-Reply-To: <1389833903.31288.1.camel@concordia> References: <1389765724.6933.78.camel@pasglop> <1389833903.31288.1.camel@concordia> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: linuxppc-dev list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2014-01-16 at 11:58 +1100, Michael Ellerman wrote: > On Wed, 2014-01-15 at 17:02 +1100, Benjamin Herrenschmidt wrote: > > From: Vasant Hegde > > > > Its possible that OPAL may be writing to host memory during > > kexec (like dump retrieve scenario). In this situation we might > > end up corrupting host memory. > > Are we happy with that happening during kdump? (which doesn't call any of the > shutdown paths) Obviously not ... There's a problem there. Not sure what the right fix is. Might need some ifdef KDUMP to take over in the new driver. Ben.