From: "Oliver O'Halloran" <email@example.com> To: Tiezhu Yang <firstname.lastname@example.org> Cc: Bjorn Helgaas <email@example.com>, Bjorn Helgaas <firstname.lastname@example.org>, linux-pci <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, "Rafael J. Wysocki" <email@example.com>, Xuefeng Li <firstname.lastname@example.org>, Huacai Chen <email@example.com>, Jiaxun Yang <firstname.lastname@example.org> Subject: Re: [RFC PATCH] PCI/portdrv: No need to call pci_disable_device() during shutdown Date: Fri, 11 Sep 2020 12:35:41 +1000 [thread overview] Message-ID: <CAOSf1CGM0SV2ux-TYv_N2frgZtqin8yfvh1wUDj+oMVmjr3GHQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Fri, Sep 11, 2020 at 11:55 AM Tiezhu Yang <firstname.lastname@example.org> wrote: > > On 09/11/2020 04:21 AM, Bjorn Helgaas wrote: > > [+cc Huacai] > > > > On Thu, Sep 10, 2020 at 02:41:39PM -0500, Bjorn Helgaas wrote: > >> On Sat, Sep 05, 2020 at 04:33:26PM +0800, Tiezhu Yang wrote: > >>> 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 seems unnecessary, so just remove it. > >> I would like to get rid of the portdrv completely by folding its > >> functionality into the PCI core itself, so there would be no portdrv > >> probe or remove. > >> > >> Does this solve a problem? > > Yes, sometimes it can not shutdown or reboot normally with > pci_disable_device(). Do you have any more details about what goes wrong here? Leaving devices enabled when actually shutting down probably doesn't matter. However, .shutdown() is also used when kexec()ing into a new kernel and we probably should be disabling devices before handing over to the new kernel. Is the real issue that we're closing the bridge windows before the endpoint drivers have had a chance to clean up? Oliver
next prev parent reply other threads:[~2020-09-11 2:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-05 8:33 Tiezhu Yang 2020-09-10 19:41 ` Bjorn Helgaas 2020-09-10 20:21 ` Bjorn Helgaas 2020-09-11 1:54 ` Tiezhu Yang 2020-09-11 2:35 ` Oliver O'Halloran [this message] 2020-09-11 3:19 ` Tiezhu Yang
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=CAOSf1CGM0SV2ux-TYv_N2frgZtqin8yfvh1wUDj+oMVmjr3GHQ@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [RFC PATCH] PCI/portdrv: No need to call pci_disable_device() during shutdown' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.