On Thu, Aug 01, 2013 at 03:34:06PM +0900, Takao Indoh wrote:
> (2013/08/01 6:23), Rafael J. Wysocki wrote:
> > On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
> >> [+cc Rafael, linux-acpi]
> >>
> >> On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh
> >> wrote:
> >>
> >>> On x86,
On Thu, 2013-08-01 at 15:34 +0900, Takao Indoh wrote:
> (2013/08/01 6:23), Rafael J. Wysocki wrote:
> > On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
> >> [+cc Rafael, linux-acpi]
> >>
> >> On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh
> >> wrote:
> >>
> >>> On x86, currently IOMMU
(2013/08/01 6:23), Rafael J. Wysocki wrote:
> On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
>> [+cc Rafael, linux-acpi]
>>
>> On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh
>> wrote:
>>
>>> On x86, currently IOMMU initialization run *after* PCI enumeration, but
>>> what you are
(2013/08/01 6:23), Rafael J. Wysocki wrote:
On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
[+cc Rafael, linux-acpi]
On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
On x86, currently IOMMU initialization run *after* PCI enumeration, but
what you
On Thu, 2013-08-01 at 15:34 +0900, Takao Indoh wrote:
(2013/08/01 6:23), Rafael J. Wysocki wrote:
On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
[+cc Rafael, linux-acpi]
On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
On x86, currently
On Thu, Aug 01, 2013 at 03:34:06PM +0900, Takao Indoh wrote:
(2013/08/01 6:23), Rafael J. Wysocki wrote:
On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
[+cc Rafael, linux-acpi]
On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
On x86,
On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
> [+cc Rafael, linux-acpi]
>
> On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh
> wrote:
>
> > On x86, currently IOMMU initialization run *after* PCI enumeration, but
> > what you are talking about is that it should be changed so that
[+cc Rafael, linux-acpi]
On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh wrote:
> On x86, currently IOMMU initialization run *after* PCI enumeration, but
> what you are talking about is that it should be changed so that x86
> IOMMU initialization is done *before* PCI enumeration like sparc, right?
On Tue, Jul 30, 2013 at 09:59:16AM -0600, Bjorn Helgaas wrote:
> On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
> wrote:
> > (2013/07/29 23:17), Bjorn Helgaas wrote:
> >> On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh
> >> wrote:
> >>> (2013/07/26 2:00), Bjorn Helgaas wrote:
>
> My point
On Thu, Jul 25, 2013 at 11:00:46AM -0600, Bjorn Helgaas wrote:
> On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
> wrote:
> > Sorry for letting this discussion slide, I was busy on other works:-(
> > Anyway, the summary of previous discussion is:
> > - My patch adds new initcall(fs_initcall) to
On Thu, Jul 25, 2013 at 11:00:46AM -0600, Bjorn Helgaas wrote:
On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of previous discussion is:
- My patch adds new
On Tue, Jul 30, 2013 at 09:59:16AM -0600, Bjorn Helgaas wrote:
On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
(2013/07/29 23:17), Bjorn Helgaas wrote:
On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
(2013/07/26 2:00), Bjorn
[+cc Rafael, linux-acpi]
On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh indou.ta...@jp.fujitsu.com wrote:
On x86, currently IOMMU initialization run *after* PCI enumeration, but
what you are talking about is that it should be changed so that x86
IOMMU initialization is done *before* PCI
On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
[+cc Rafael, linux-acpi]
On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
On x86, currently IOMMU initialization run *after* PCI enumeration, but
what you are talking about is that it should be
(2013/07/31 12:11), Alex Williamson wrote:
> On Wed, 2013-07-31 at 09:35 +0900, Takao Indoh wrote:
>> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
>> index e37fea6..c595997 100644
>> --- a/drivers/pci/pci.c
>> +++ b/drivers/pci/pci.c
>> @@ -3392,6 +3392,59 @@ int pci_reset_function(struct
On Wed, 2013-07-31 at 09:35 +0900, Takao Indoh wrote:
> (2013/07/31 0:59), Bjorn Helgaas wrote:
> > On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
> > wrote:
> >> (2013/07/29 23:17), Bjorn Helgaas wrote:
> >>> On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh
> >>> wrote:
> (2013/07/26 2:00),
(2013/07/31 0:59), Bjorn Helgaas wrote:
> On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
> wrote:
>> (2013/07/29 23:17), Bjorn Helgaas wrote:
>>> On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh
>>> wrote:
(2013/07/26 2:00), Bjorn Helgaas wrote:
>
> My point about IOMMU and PCI
On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
wrote:
> (2013/07/29 23:17), Bjorn Helgaas wrote:
>> On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh
>> wrote:
>>> (2013/07/26 2:00), Bjorn Helgaas wrote:
My point about IOMMU and PCI initialization order doesn't go away just
because it
(2013/07/29 23:17), Bjorn Helgaas wrote:
> On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh
> wrote:
>> (2013/07/26 2:00), Bjorn Helgaas wrote:
>>> On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
>>> wrote:
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the
(2013/07/29 23:17), Bjorn Helgaas wrote:
On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
(2013/07/26 2:00), Bjorn Helgaas wrote:
On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
Sorry for letting this discussion slide, I was busy
On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
(2013/07/29 23:17), Bjorn Helgaas wrote:
On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
(2013/07/26 2:00), Bjorn Helgaas wrote:
My point about IOMMU and PCI initialization order
(2013/07/31 0:59), Bjorn Helgaas wrote:
On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
(2013/07/29 23:17), Bjorn Helgaas wrote:
On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
(2013/07/26 2:00), Bjorn Helgaas wrote:
My point
On Wed, 2013-07-31 at 09:35 +0900, Takao Indoh wrote:
(2013/07/31 0:59), Bjorn Helgaas wrote:
On Tue, Jul 30, 2013 at 12:09 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
(2013/07/29 23:17), Bjorn Helgaas wrote:
On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh indou.ta...@jp.fujitsu.com
(2013/07/31 12:11), Alex Williamson wrote:
On Wed, 2013-07-31 at 09:35 +0900, Takao Indoh wrote:
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index e37fea6..c595997 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -3392,6 +3392,59 @@ int pci_reset_function(struct pci_dev *dev)
On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh wrote:
> (2013/07/26 2:00), Bjorn Helgaas wrote:
>> On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
>> wrote:
>>> Sorry for letting this discussion slide, I was busy on other works:-(
>>> Anyway, the summary of previous discussion is:
>>> - My patch
On Sun, Jul 28, 2013 at 6:37 PM, Takao Indoh indou.ta...@jp.fujitsu.com wrote:
(2013/07/26 2:00), Bjorn Helgaas wrote:
On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of
(2013/07/26 2:00), Bjorn Helgaas wrote:
> On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
> wrote:
>> Sorry for letting this discussion slide, I was busy on other works:-(
>> Anyway, the summary of previous discussion is:
>> - My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
(2013/07/25 23:24), Vivek Goyal wrote:
> On Wed, Jul 24, 2013 at 03:29:58PM +0900, Takao Indoh wrote:
>> Sorry for letting this discussion slide, I was busy on other works:-(
>> Anyway, the summary of previous discussion is:
>> - My patch adds new initcall(fs_initcall) to reset all PCIe endpoints
(2013/07/25 23:24), Vivek Goyal wrote:
On Wed, Jul 24, 2013 at 03:29:58PM +0900, Takao Indoh wrote:
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of previous discussion is:
- My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
(2013/07/26 2:00), Bjorn Helgaas wrote:
On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of previous discussion is:
- My patch adds new initcall(fs_initcall) to reset all
On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
wrote:
> Sorry for letting this discussion slide, I was busy on other works:-(
> Anyway, the summary of previous discussion is:
> - My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
> boot. This expects PCI enumeration is done
On Wed, Jul 24, 2013 at 03:29:58PM +0900, Takao Indoh wrote:
> Sorry for letting this discussion slide, I was busy on other works:-(
> Anyway, the summary of previous discussion is:
> - My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
> boot. This expects PCI enumeration is
On Wed, Jul 24, 2013 at 03:29:58PM +0900, Takao Indoh wrote:
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of previous discussion is:
- My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
boot. This expects PCI enumeration is
On Wed, Jul 24, 2013 at 12:29 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of previous discussion is:
- My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
boot. This expects PCI
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of previous discussion is:
- My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
boot. This expects PCI enumeration is done before IOMMU
initialization as follows.
(1) PCI
Sorry for letting this discussion slide, I was busy on other works:-(
Anyway, the summary of previous discussion is:
- My patch adds new initcall(fs_initcall) to reset all PCIe endpoints on
boot. This expects PCI enumeration is done before IOMMU
initialization as follows.
(1) PCI
(2013/06/13 12:41), Bjorn Helgaas wrote:
> On Wed, Jun 12, 2013 at 8:44 PM, Takao Indoh
> wrote:
>> (2013/06/12 13:45), Bjorn Helgaas wrote:
>>> [+cc Vivek, Haren; sorry I didn't think to add you earlier]
>>>
>>> On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
>>> wrote:
(2013/06/11 11:20),
(2013/06/13 12:41), Bjorn Helgaas wrote:
On Wed, Jun 12, 2013 at 8:44 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
(2013/06/12 13:45), Bjorn Helgaas wrote:
[+cc Vivek, Haren; sorry I didn't think to add you earlier]
On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
On Wed, Jun 12, 2013 at 8:44 PM, Takao Indoh wrote:
> (2013/06/12 13:45), Bjorn Helgaas wrote:
>> [+cc Vivek, Haren; sorry I didn't think to add you earlier]
>>
>> On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
>> wrote:
>>> (2013/06/11 11:20), Bjorn Helgaas wrote:
>>
I'm not sure you need
(2013/06/12 22:19), Don Dutile wrote:
> On 06/11/2013 07:19 PM, Sumner, William wrote:
>>
>>> (2013/06/11 11:20), Bjorn Helgaas wrote:
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh
wrote:
> (2013/06/07 13:14), Bjorn Helgaas wrote:
>> One thing I'm not sure about is that you
(2013/06/12 13:45), Bjorn Helgaas wrote:
> [+cc Vivek, Haren; sorry I didn't think to add you earlier]
>
> On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
> wrote:
>> (2013/06/11 11:20), Bjorn Helgaas wrote:
>
>>> I'm not sure you need to reset legacy devices (or non-PCI devices)
>>> yet, but the
On 06/11/2013 07:19 PM, Sumner, William wrote:
(2013/06/11 11:20), Bjorn Helgaas wrote:
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh wrote:
(2013/06/07 13:14), Bjorn Helgaas wrote:
One thing I'm not sure about is that you are only resetting PCIe
devices, but I don't think the problem is
On 06/11/2013 07:19 PM, Sumner, William wrote:
(2013/06/11 11:20), Bjorn Helgaas wrote:
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indohindou.ta...@jp.fujitsu.com wrote:
(2013/06/07 13:14), Bjorn Helgaas wrote:
One thing I'm not sure about is that you are only resetting PCIe
devices, but I
(2013/06/12 13:45), Bjorn Helgaas wrote:
[+cc Vivek, Haren; sorry I didn't think to add you earlier]
On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
(2013/06/11 11:20), Bjorn Helgaas wrote:
I'm not sure you need to reset legacy devices (or non-PCI devices)
(2013/06/12 22:19), Don Dutile wrote:
On 06/11/2013 07:19 PM, Sumner, William wrote:
(2013/06/11 11:20), Bjorn Helgaas wrote:
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indohindou.ta...@jp.fujitsu.com
wrote:
(2013/06/07 13:14), Bjorn Helgaas wrote:
One thing I'm not sure about is that you are
On Wed, Jun 12, 2013 at 8:44 PM, Takao Indoh indou.ta...@jp.fujitsu.com wrote:
(2013/06/12 13:45), Bjorn Helgaas wrote:
[+cc Vivek, Haren; sorry I didn't think to add you earlier]
On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
(2013/06/11 11:20), Bjorn
[+cc Vivek, Haren; sorry I didn't think to add you earlier]
On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
wrote:
> (2013/06/11 11:20), Bjorn Helgaas wrote:
>> I'm not sure you need to reset legacy devices (or non-PCI devices)
>> yet, but the current hook isn't anchored anywhere -- it's just an
[Your quoting is messed up below]
>> This is Takao's text
> This is Bill's text
On Tue, Jun 11, 2013 at 5:19 PM, Sumner, William wrote:
>>(2013/06/11 11:20), Bjorn Helgaas wrote:
>>> On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh
>>> wrote:
>>Actually Vivek Goyal, kdump maintainer said same
>(2013/06/11 11:20), Bjorn Helgaas wrote:
>> On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh
>> wrote:
>>> (2013/06/07 13:14), Bjorn Helgaas wrote:
>>
One thing I'm not sure about is that you are only resetting PCIe
devices, but I don't think the problem is actually specific to PCIe,
(2013/06/11 11:20), Bjorn Helgaas wrote:
> On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh
> wrote:
>> (2013/06/07 13:14), Bjorn Helgaas wrote:
>
>>> One thing I'm not sure about is that you are only resetting PCIe
>>> devices, but I don't think the problem is actually specific to PCIe,
>>> is it?
(2013/06/11 11:20), Bjorn Helgaas wrote:
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
(2013/06/07 13:14), Bjorn Helgaas wrote:
One thing I'm not sure about is that you are only resetting PCIe
devices, but I don't think the problem is actually specific to
(2013/06/11 11:20), Bjorn Helgaas wrote:
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
(2013/06/07 13:14), Bjorn Helgaas wrote:
One thing I'm not sure about is that you are only resetting PCIe
devices, but I don't think the problem is actually specific to
[Your quoting is messed up below]
This is Takao's text
This is Bill's text
On Tue, Jun 11, 2013 at 5:19 PM, Sumner, William bill.sum...@hp.com wrote:
(2013/06/11 11:20), Bjorn Helgaas wrote:
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
Actually Vivek Goyal,
[+cc Vivek, Haren; sorry I didn't think to add you earlier]
On Tue, Jun 11, 2013 at 12:08 AM, Takao Indoh
indou.ta...@jp.fujitsu.com wrote:
(2013/06/11 11:20), Bjorn Helgaas wrote:
I'm not sure you need to reset legacy devices (or non-PCI devices)
yet, but the current hook isn't anchored
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh wrote:
> (2013/06/07 13:14), Bjorn Helgaas wrote:
>> One thing I'm not sure about is that you are only resetting PCIe
>> devices, but I don't think the problem is actually specific to PCIe,
>> is it? I think the same issue could occur on any system
On Fri, Jun 7, 2013 at 2:46 AM, Takao Indoh indou.ta...@jp.fujitsu.com wrote:
(2013/06/07 13:14), Bjorn Helgaas wrote:
One thing I'm not sure about is that you are only resetting PCIe
devices, but I don't think the problem is actually specific to PCIe,
is it? I think the same issue could
Thank you for your comments!
(2013/06/07 13:14), Bjorn Helgaas wrote:
> Sorry it's taken me so long to look at this. I've been putting this
> off because the patch doesn't seem "obviously correct," and I don't
> feel like I really understand the problem. I'm naive about both
> IOMMUs and
Thank you for your comments!
(2013/06/07 13:14), Bjorn Helgaas wrote:
Sorry it's taken me so long to look at this. I've been putting this
off because the patch doesn't seem obviously correct, and I don't
feel like I really understand the problem. I'm naive about both
IOMMUs and kexec/kdump,
Sorry it's taken me so long to look at this. I've been putting this
off because the patch doesn't seem "obviously correct," and I don't
feel like I really understand the problem. I'm naive about both
IOMMUs and kexec/kdump, so please pardon (and help me with) any silly
questions or assumptions
Ping
Bjorn, could you please tell your impression on this idea?
This fix is very important for kdump. For exmaple, kdump does not work
if PCI passthrough is used on KVM guest. Please see patch description
for details.
If you don't agree this patch, please tell me what changes I should
make.
Ping
Bjorn, could you please tell your impression on this idea?
This fix is very important for kdump. For exmaple, kdump does not work
if PCI passthrough is used on KVM guest. Please see patch description
for details.
If you don't agree this patch, please tell me what changes I should
make.
Sorry it's taken me so long to look at this. I've been putting this
off because the patch doesn't seem obviously correct, and I don't
feel like I really understand the problem. I'm naive about both
IOMMUs and kexec/kdump, so please pardon (and help me with) any silly
questions or assumptions
Hi Bjorn,
Any comments, ack/nack?
Thanks,
Takao Indoh
(2013/05/15 7:04), Eric W. Biederman wrote:
> Takao Indoh writes:
>
>> This patch resets PCIe devices on boot to stop ongoing DMA. When
>> "pci=pcie_reset_endpoint_devices" is specified, a hot reset is triggered
>> on each PCIe root port
Hi Bjorn,
Any comments, ack/nack?
Thanks,
Takao Indoh
(2013/05/15 7:04), Eric W. Biederman wrote:
Takao Indoh indou.ta...@jp.fujitsu.com writes:
This patch resets PCIe devices on boot to stop ongoing DMA. When
pci=pcie_reset_endpoint_devices is specified, a hot reset is triggered
on each
Takao Indoh writes:
> This patch resets PCIe devices on boot to stop ongoing DMA. When
> "pci=pcie_reset_endpoint_devices" is specified, a hot reset is triggered
> on each PCIe root port and downstream port to reset its downstream
> endpoint.
>
> Problem:
> This patch solves the problem that
Takao Indoh indou.ta...@jp.fujitsu.com writes:
This patch resets PCIe devices on boot to stop ongoing DMA. When
pci=pcie_reset_endpoint_devices is specified, a hot reset is triggered
on each PCIe root port and downstream port to reset its downstream
endpoint.
Problem:
This patch solves the
This patch resets PCIe devices on boot to stop ongoing DMA. When
"pci=pcie_reset_endpoint_devices" is specified, a hot reset is triggered
on each PCIe root port and downstream port to reset its downstream
endpoint.
Problem:
This patch solves the problem that kdump can fail when intel_iommu=on is
This patch resets PCIe devices on boot to stop ongoing DMA. When
pci=pcie_reset_endpoint_devices is specified, a hot reset is triggered
on each PCIe root port and downstream port to reset its downstream
endpoint.
Problem:
This patch solves the problem that kdump can fail when intel_iommu=on is
68 matches
Mail list logo
