From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@gmail.com>, Bjorn Helgaas <bhelgaas@google.com>
Cc: Konstantin Khlebnikov <khlebnikov@openvz.org>,
Khalid Aziz <khalid.aziz@oracle.com>,
Vivek Goyal <vgoyal@redhat.com>, Lukas Wunner <lukas@wunner.de>,
oohall <oohall@gmail.com>,
"rafael.j.wysocki" <rafael.j.wysocki@intel.com>,
Xuefeng Li <lixuefeng@loongson.cn>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-pci <linux-pci@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
zhouyanjie <zhouyanjie@wanyeetech.com>, git <git@xen0n.name>
Subject: Re: [RFC PATCH v2] PCI/portdrv: Only disable Bus Master on kexec reboot and connected PCI devices
Date: Mon, 14 Sep 2020 14:17:15 +0800 [thread overview]
Message-ID: <939d35d9-bbe7-3fef-7fc6-ff331d8f5010@loongson.cn> (raw)
In-Reply-To: <CAAhV-H5-X9OcBe3iRxF8PnKW-0j_10FVqm8cbiqW2-Lv4mTTdQ@mail.gmail.com>
On 09/14/2020 12:31 PM, Huacai Chen wrote:
> Hi, Tiezhu
>
>> ------------------ Original ------------------
>> From: "Tiezhu Yang"<yangtiezhu@loongson.cn>;
>> Date: Mon, Sep 14, 2020 04:29 AM
>> To: "Bjorn Helgaas"<bhelgaas@google.com>;
>> Cc: "Konstantin Khlebnikov"<khlebnikov@openvz.org>; "Khalid Aziz"<khalid.aziz@oracle.com>; "Vivek Goyal"<vgoyal@redhat.com>; "Lukas Wunner"<lukas@wunner.de>; "oohall"<oohall@gmail.com>; "rafael.j.wysocki"<rafael.j.wysocki@intel.com>; "Xuefeng Li"<lixuefeng@loongson.cn>; "Huacai Chen"<chenhc@lemote.com>; "Jiaxun Yang"<jiaxun.yang@flygoat.com>; "linux-pci"<linux-pci@vger.kernel.org>; "linux-kernel"<linux-kernel@vger.kernel.org>;
>> Subject: [RFC PATCH v2] PCI/portdrv: Only disable Bus Master on kexec reboot and connected PCI devices
>>
>>
>>
>> After commit 745be2e700cd ("PCIe: portdrv: call pci_disable_device
>> during remove") and commit cc27b735ad3a ("PCI/portdrv: Turn off PCIe
>> services during shutdown"), it also calls pci_disable_device() during
>> shutdown, this leads to shutdown or reboot failure occasionally due to
>> clear PCI_COMMAND_MASTER on the device in do_pci_disable_device().
>>
>> drivers/pci/pci.c
>> static void do_pci_disable_device(struct pci_dev *dev)
>> {
>> u16 pci_command;
>>
>> pci_read_config_word(dev, PCI_COMMAND, &pci_command);
>> if (pci_command & PCI_COMMAND_MASTER) {
>> pci_command &= ~PCI_COMMAND_MASTER;
>> pci_write_config_word(dev, PCI_COMMAND, pci_command);
>> }
>>
>> pcibios_disable_device(dev);
>> }
>>
>> When remove "pci_command &= ~PCI_COMMAND_MASTER;", it can work well.
>>
>> As Oliver O'Halloran said, no need to call pci_disable_device() when
>> actually shutting down, but we should call pci_disable_device() before
>> handing over to the new kernel on kexec reboot, so we can do some
>> condition checks which are similar with pci_device_shutdown(), this is
>> done by commit 4fc9bbf98fd6 ("PCI: Disable Bus Master only on kexec
>> reboot") and commit 6e0eda3c3898 ("PCI: Don't try to disable Bus Master
>> on disconnected PCI devices").
>>
>> drivers/pci/pci-driver.c
>> static void pci_device_shutdown(struct device *dev)
>> {
>> ...
>>
>> /*
>> * If this is a kexec reboot, turn off Bus Master bit on the
>> * device to tell it to not continue to do DMA. Don't touch
>> * devices in D3cold or unknown states.
>> * If it is not a kexec reboot, firmware will hit the PCI
>> * devices with big hammer and stop their DMA any way.
>> */
>> if (kexec_in_progress && (pci_dev->current_state <= PCI_D3hot))
>> pci_clear_master(pci_dev);
>> }
> Have you really tried kexec? Why do you think kexec can disable pci
> device successfully while normal reboot/poweroff cannot?
Yes, I test it on kexec reboot, it works well.
>
> Huacai
>> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
>> ---
>> drivers/pci/pcie/portdrv_core.c | 1 -
>> drivers/pci/pcie/portdrv_pci.c | 25 ++++++++++++++++++++++++-
>> 2 files changed, 24 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
>> index 50a9522..1991aca 100644
>> --- a/drivers/pci/pcie/portdrv_core.c
>> +++ b/drivers/pci/pcie/portdrv_core.c
>> @@ -491,7 +491,6 @@ void pcie_port_device_remove(struct pci_dev *dev)
>> {
>> device_for_each_child(&dev->dev, NULL, remove_iter);
>> pci_free_irq_vectors(dev);
>> - pci_disable_device(dev);
>> }
>>
>> /**
>> diff --git a/drivers/pci/pcie/portdrv_pci.c b/drivers/pci/pcie/portdrv_pci.c
>> index 3a3ce40..ce89a9e8 100644
>> --- a/drivers/pci/pcie/portdrv_pci.c
>> +++ b/drivers/pci/pcie/portdrv_pci.c
>> @@ -15,6 +15,7 @@
>> #include <linux/init.h>
>> #include <linux/aer.h>
>> #include <linux/dmi.h>
>> +#include <linux/kexec.h>
>>
>> #include "../pci.h"
>> #include "portdrv.h"
>> @@ -143,6 +144,28 @@ static void pcie_portdrv_remove(struct pci_dev *dev)
>> }
>>
>> pcie_port_device_remove(dev);
>> + pci_disable_device(dev);
>> +}
>> +
>> +static void pcie_portdrv_shutdown(struct pci_dev *dev)
>> +{
>> + if (pci_bridge_d3_possible(dev)) {
>> + pm_runtime_forbid(&dev->dev);
>> + pm_runtime_get_noresume(&dev->dev);
>> + pm_runtime_dont_use_autosuspend(&dev->dev);
>> + }
>> +
>> + pcie_port_device_remove(dev);
>> +
>> + /*
>> + * If this is a kexec reboot, turn off Bus Master bit on the
>> + * device to tell it to not continue to do DMA. Don't touch
>> + * devices in D3cold or unknown states.
>> + * If it is not a kexec reboot, firmware will hit the PCI
>> + * devices with big hammer and stop their DMA any way.
>> + */
>> + if (kexec_in_progress && (dev->current_state <= PCI_D3hot))
>> + pci_disable_device(dev);
>> }
>>
>> static pci_ers_result_t pcie_portdrv_error_detected(struct pci_dev *dev,
>> @@ -211,7 +234,7 @@ static void pcie_portdrv_err_resume(struct pci_dev *dev)
>>
>> .probe = pcie_portdrv_probe,
>> .remove = pcie_portdrv_remove,
>> - .shutdown = pcie_portdrv_remove,
>> + .shutdown = pcie_portdrv_shutdown,
>>
>> .err_handler = &pcie_portdrv_err_handler,
>>
>> --
>> 1.8.3.1
prev parent reply other threads:[~2020-09-14 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 20:29 Tiezhu Yang
2020-09-14 4:06 ` Lukas Wunner
2020-09-14 6:13 ` Tiezhu Yang
2020-09-14 6:30 ` Tiezhu Yang
[not found] ` <tencent_44F0201A70619BA613F16BA4@qq.com>
2020-09-14 4:31 ` Huacai Chen
2020-09-14 6:17 ` Tiezhu Yang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=939d35d9-bbe7-3fef-7fc6-ff331d8f5010@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=bhelgaas@google.com \
--cc=chenhuacai@gmail.com \
--cc=git@xen0n.name \
--cc=jiaxun.yang@flygoat.com \
--cc=khalid.aziz@oracle.com \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=lukas@wunner.de \
--cc=oohall@gmail.com \
--cc=rafael.j.wysocki@intel.com \
--cc=vgoyal@redhat.com \
--cc=zhouyanjie@wanyeetech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®