[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <506B8D7B.8090004@jp.fujitsu.com>
Date: Wed, 03 Oct 2012 09:57:31 +0900
From: Takao Indoh <indou.takao@...fujitsu.com>
To: andi@...stfloor.org
CC: linux-pci@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org, martin.wilck@...fujitsu.com,
kexec@...ts.infradead.org, hbabu@...ibm.com, mingo@...hat.com,
vgoyal@...hat.com, ishii.hironobu@...fujitsu.com, hpa@...or.com,
bhelgaas@...gle.com, tglx@...utronix.de
Subject: Re: [PATCH v2 0/2] Reset PCIe devices to address DMA problem on kdump
with iommu
(2012/10/03 4:37), Andi Kleen wrote:
> Takao Indoh <indou.takao@...fujitsu.com> 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.
Actually I got the idea of this patch from your comment below;-)
http://permalink.gmane.org/gmane.linux.network/162414
>
> Now the only question is: why make it a option and not default?
Except kdump I don't know the situation where this reset is useful, so I
introduced it as option so that it works only during kdump.
Thanks,
Takao Indoh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists