From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com ([143.182.124.21]:3589 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751732Ab2JBThq (ORCPT ); Tue, 2 Oct 2012 15:37:46 -0400 From: Andi Kleen To: Takao Indoh Cc: linux-pci@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, martin.wilck@ts.fujitsu.com, kexec@lists.infradead.org, hbabu@us.ibm.com, mingo@redhat.com, vgoyal@redhat.com, ishii.hironobu@jp.fujitsu.com, hpa@zytor.com, bhelgaas@google.com, tglx@linutronix.de Subject: Re: [PATCH v2 0/2] Reset PCIe devices to address DMA problem on kdump with iommu References: <20121002074434.204.47750.sendpatchset@indoh> Date: Tue, 02 Oct 2012 12:37:44 -0700 In-Reply-To: <20121002074434.204.47750.sendpatchset@indoh> (Takao Indoh's message of "Tue, 2 Oct 2012 16:49:56 +0900 (JST)") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-pci-owner@vger.kernel.org List-ID: Takao Indoh writes: > These patches reset PCIe devices at boot time to address DMA problem on > kdump with iommu. When "reset_devices" is specified, a hot reset is > triggered on each PCIe root port and downstream port to reset its > downstream endpoint. Great. I've been pondering this for a long time, but you did finally implement it. I hope this will make kdump a lot more reliable at least on the systems that support per port reset. Now the only question is: why make it a option and not default? -Andi -- ak@linux.intel.com -- Speaking for myself only