Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753888AbXJaTrl (ORCPT ); Wed, 31 Oct 2007 15:47:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752486AbXJaTra (ORCPT ); Wed, 31 Oct 2007 15:47:30 -0400 Received: from mtagate8.de.ibm.com ([195.212.29.157]:40945 "EHLO mtagate8.de.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752204AbXJaTr3 (ORCPT ); Wed, 31 Oct 2007 15:47:29 -0400 In-Reply-To: <1193784636.32504.4.camel@concordia> References: <200710261437.29117.ossthema@de.ibm.com> <1193610737.9637.1.camel@concordia> <1193784636.32504.4.camel@concordia> Subject: Re: [PATCH] ehea: add kexec support To: michael@ellerman.id.au Cc: Jan-Bernd Themann , Jeff Garzik , linux-kernel , linux-ppc , Marcus Eder , netdev , ossthema@linux.vnet.ibm.com, Stefan Roscher , Thomas Q Klein X-Mailer: Lotus Notes Release 8.0 August 02, 2007 Message-ID: From: Christoph Raisch Date: Wed, 31 Oct 2007 20:48:28 +0100 X-MIMETrack: Serialize by Router on D12ML067/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 31/10/2007 20:47:26 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1373 Lines: 36 Michael Ellerman wrote on 30.10.2007 23:50:36: > > On Tue, 2007-10-30 at 09:39 +0100, Christoph Raisch wrote: > > > > Michael Ellerman wrote on 28.10.2007 23:32:17: > > Hope I didn't miss anything here... > > Perhaps. When we kdump the kernel does not call the reboot notifiers, so > the code Jan-Bernd just added won't get called. So the eHEA resources > won't be freed. When the kdump kernel tries to load the eHEA driver what > will happen? > Good point. If the device driver tries to allocate resources again (in the kdump kernel), which have been allocated before (in the crashed kernel) the hcalls will fail because from the hypervisor view the resources are still in use. Currently there's no method to find out the resource handles for these HEA resources allocated by the crashed kernel within the hypervisor... So we have to trigger a explicit deregister in the hypervisor before the driver is started again. How do you recommend we should trigger this in the kdump process? Is placing a hook into a ppc_md.machine_kexec be an option? Gruss / Regards Christoph R. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/