Received: by 10.192.165.148 with SMTP id m20csp785881imm; Thu, 10 May 2018 00:03:32 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoH2HlTtTRwpWfVZupOAYPWYvEVuYiBAIMOvzT86XYl5pehJvZK0zzbqp2EC/sG/nJJZyAa X-Received: by 2002:a63:6706:: with SMTP id b6-v6mr196526pgc.214.1525935812306; Thu, 10 May 2018 00:03:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525935812; cv=none; d=google.com; s=arc-20160816; b=ejY737Xotyc5tMN+8IctGvXjthAcuPv0gJDabCYmO+NYsyDX28YYJTlE2gpxNCQoKD ArYh0QAmFZiFHs1IgfC88EV6hsii1YQxLZfC+wRgkP4kBKMpx1chZOOZ8oiSLsFDSQXB 97FNXNlvsRWvZ5mX+RgsTZcfDXH+KhOO+DgwfJiA9CroT65GL1lkjptvNtP842qpmGqF HHSUw0j8h0naqDkPyp9Pi2Z/qDL+sJvaM/YUEwkeBP0MUpDW5zNnlPGIoqQHoyiD7gE1 PJFX9aTXhYS9efW24E4wk73WbO/pcT1LmMcS1A8HZfhcGgP0vTXMH/+PBG2TDDVxUgVs niKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=u2NilxRpuVkM9oz6b8+YVgNmWJo+SOps/fsB2jiEzYY=; b=04FZmYwiiwgkSvcim/oTN0qE6H5d6nV2YFcXrolw/yBjA15JRnyhmZKtZNmXU0e8wb WsC6x9PyKI0lIIbURiHUs5waT/8acdCb/iKVd1GOKSFz16sCCmEpFHT2NH2JPYwI5FaD rsS3+mLKFl+4I8yz1DnI8J+eiCpeBopn6ljpV0c1RkOvrEzf/M5ap5zkcsqYp0mnGwSZ 1cViewVlKtuQ24/Yue8c5vtUdhCtaj3fMoy0joDVYGVy84vPDugqxrmT/FWRrSlftL7A M5NHUN8kWI/btniGLTtJIhuxPfkaB1U+wL1reD9EQNtj1uEiQBfbOZJ8m7LOJvmZPI7U VHeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=VDJjajSj; dkim=pass header.i=@codeaurora.org header.s=default header.b=hNKtxQdm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y9-v6si170120pfk.34.2018.05.10.00.03.08; Thu, 10 May 2018 00:03:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=VDJjajSj; dkim=pass header.i=@codeaurora.org header.s=default header.b=hNKtxQdm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933988AbeEJHBV (ORCPT + 99 others); Thu, 10 May 2018 03:01:21 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:39732 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756305AbeEJHBT (ORCPT ); Thu, 10 May 2018 03:01:19 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id ED4FB60A00; Thu, 10 May 2018 07:01:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525935679; bh=Jsl6UeuHYw0turJueya8EM3v+Pq3ksxUjXqz8Yz2UCo=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=VDJjajSjk7Ujoq1exyXp6G6z4XzYM98RziMrVRVOskvEft6MnAC3Qse0gufDYhqiJ 5eAHlpBKVqxTIrK5gpP8UBhYQpXhDrS/emYt48rtE5HcIGE/sJpg/MCSCttWsDKUfp Cxh3FaYlESxjZNscg8DDARdKpw66pl3I91OClyTE= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id CD3926079C; Thu, 10 May 2018 07:01:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525935676; bh=Jsl6UeuHYw0turJueya8EM3v+Pq3ksxUjXqz8Yz2UCo=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=hNKtxQdmsF9GgguGMCAHaKRssHxqc2s8P8ch7w+H0Ebmnbr2hXzHbVlkpNGMMOySj kVlwV2pgt/TAEeNQ6I703v0gyd/O7gOz2d8E1VURl+zmfvyPZnS2WQDkv7NOTBEQLc WysYAq5F9iJYoEAZFK/W+M8CzojWhoLSTDYfMYzI= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 10 May 2018 12:31:16 +0530 From: poza@codeaurora.org To: Bjorn Helgaas Cc: Bjorn Helgaas , Philippe Ombredanne , Thomas Gleixner , Greg Kroah-Hartman , Kate Stewart , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Dongdong Liu , Keith Busch , Wei Zhang , Sinan Kaya , Timur Tabi , linux-pci-owner@vger.kernel.org Subject: Re: [PATCH v15 3/9] PCI/AER: Handle ERR_FATAL with removal and re-enumeration of devices In-Reply-To: <20180509232111.GA43216@bhelgaas-glaptop.roam.corp.google.com> References: <1525323838-1735-1-git-send-email-poza@codeaurora.org> <1525323838-1735-4-git-send-email-poza@codeaurora.org> <20180508235330.GN161390@bhelgaas-glaptop.roam.corp.google.com> <20180509130730.GA236548@bhelgaas-glaptop.roam.corp.google.com> <20180509232111.GA43216@bhelgaas-glaptop.roam.corp.google.com> Message-ID: X-Sender: poza@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-05-10 04:51, Bjorn Helgaas wrote: > On Wed, May 09, 2018 at 06:44:53PM +0530, poza@codeaurora.org wrote: >> On 2018-05-09 18:37, Bjorn Helgaas wrote: >> > On Tue, May 08, 2018 at 06:53:30PM -0500, Bjorn Helgaas wrote: >> > > On Thu, May 03, 2018 at 01:03:52AM -0400, Oza Pawandeep wrote: >> > > > This patch alters the behavior of handling of ERR_FATAL, where removal >> > > > of devices is initiated, followed by reset link, followed by >> > > > re-enumeration. >> > > > >> > > > So the errors are handled in a different way as follows: >> > > > ERR_NONFATAL => call driver recovery entry points >> > > > ERR_FATAL => remove and re-enumerate >> > > > >> > > > please refer to Documentation/PCI/pci-error-recovery.txt for more details. >> > > > >> > > > Signed-off-by: Oza Pawandeep >> > > > >> > > > diff --git a/drivers/pci/pcie/aer/aerdrv.c b/drivers/pci/pcie/aer/aerdrv.c >> > > > index 779b387..206f590 100644 >> > > > --- a/drivers/pci/pcie/aer/aerdrv.c >> > > > +++ b/drivers/pci/pcie/aer/aerdrv.c >> > > > @@ -330,6 +330,13 @@ static pci_ers_result_t aer_root_reset(struct pci_dev *dev) >> > > > reg32 |= ROOT_PORT_INTR_ON_MESG_MASK; >> > > > pci_write_config_dword(dev, pos + PCI_ERR_ROOT_COMMAND, reg32); >> > > > >> > > > + /* >> > > > + * This function is called only on ERR_FATAL now, and since >> > > > + * the pci_report_resume is called only in ERR_NONFATAL case, >> > > > + * the clearing part has to be taken care here. >> > > > + */ >> > > > + aer_error_resume(dev); >> > > >> > > I don't understand this part. Previously the ERR_FATAL path looked >> > > like >> > > this: >> > > >> > > do_recovery >> > > reset_link >> > > driver->reset_link >> > > aer_root_reset >> > > pci_reset_bridge_secondary_bus # <-- reset >> > > broadcast_error_message(..., report_resume) >> > > pci_walk_bus(..., report_resume, ...) >> > > report_resume >> > > if (cb == report_resume) >> > > pci_cleanup_aer_uncorrect_error_status >> > > pci_write_config_dword(PCI_ERR_UNCOR_STATUS) # <-- clear >> > > status >> > > >> > > After this patch, it will look like this: >> > > >> > > do_recovery >> > > do_fatal_recovery >> > > pci_cleanup_aer_uncorrect_error_status >> > > pci_write_config_dword(PCI_ERR_UNCOR_STATUS) # <-- clear >> > > status >> > > reset_link >> > > driver->reset_link >> > > aer_root_reset >> > > pci_reset_bridge_secondary_bus # <-- reset >> > > aer_error_resume >> > > pcie_capability_write_word(PCI_EXP_DEVSTA) # >> > > <-- clear more >> > > pci_write_config_dword(PCI_ERR_UNCOR_STATUS) # >> > > <-- clear status >> > > >> > > So if I'm understanding correctly, the new path clears the status too >> > > early, then clears it again (plus clearing DEVSTA, which we didn't do >> > > before) later. >> > > >> > > I would think we would want to leave aer_root_reset() alone, and >> > > just move >> > > the pci_cleanup_aer_uncorrect_error_status() in do_fatal_recovery() >> > > down so >> > > it happens after we call reset_link(). That way the reset/clear >> > > sequence >> > > would be the same as it was before. >> > >> > I've been fiddling with this a bit myself and will post the results to >> > see >> > what you think. >> >> >> ok so you are suggesting to move >> pci_cleanup_aer_uncorrect_error_status down >> which I can do. >> >> And not to call aer_error_resume, because you think its clearing the >> status >> again. >> >> following code: calls aer_error_resume. >> pci_broadcast_error_message() >> /* >> * If the error is reported by an end point, we think >> this >> * error is related to the upstream link of the end >> point. >> */ >> if (state == pci_channel_io_normal) >> /* >> * the error is non fatal so the bus is ok, >> just >> invoke >> * the callback for the function that logged >> the >> error. >> */ >> cb(dev, &result_data); >> else >> pci_walk_bus(dev->bus, cb, &result_data); > > Holy crap, I thought this could not possibly get any more complicated, > but you're right; we do actually call aer_error_resume() today via an > extremely convoluted path: > > do_recovery(pci_dev) > broadcast_error_message(..., error_detected, ...) > if (AER_FATAL) > reset_link(pci_dev) > udev = BRIDGE ? pci_dev : pci_dev->bus->self > driver->reset_link(udev) > aer_root_reset(udev) > if (CAN_RECOVER) > broadcast_error_message(..., mmio_enabled, ...) > if (NEED_RESET) > broadcast_error_message(..., slot_reset, ...) > broadcast_error_message(dev, ..., report_resume, ...) > if (BRIDGE) > report_resume > driver->resume > pcie_portdrv_err_resume > device_for_each_child(..., resume_iter) > resume_iter > driver->error_resume > aer_error_resume > pci_cleanup_aer_uncorrect_error_status(pci_dev) # only if > BRIDGE > pci_write_config_dword(PCI_ERR_UNCOR_STATUS) > > aerdriver is the only port service driver that implements > .error_resume(), and aerdriver only binds to root ports. I can't > really believe all these device_for_each_child()/resume_iter() > gyrations are necessary when this is AER code calling AER code. > > Bjorn here is the code of do_fatal_recovery, where I have moved the things down and doing only if it is bridge. let me know how this looks to you, so then I can post v16. static pci_ers_result_t do_fatal_recovery(struct pci_dev *dev, int severity) { struct pci_dev *udev; struct pci_bus *parent; struct pci_dev *pdev, *temp; struct aer_broadcast_data result_data; pci_ers_result_t result = PCI_ERS_RESULT_RECOVERED; if (dev->hdr_type == PCI_HEADER_TYPE_BRIDGE) udev = dev; else udev = dev->bus->self; parent = udev->subordinate; pci_lock_rescan_remove(); list_for_each_entry_safe_reverse(pdev, temp, &parent->devices, bus_list) { pci_dev_get(pdev); pci_dev_set_disconnected(pdev, NULL); if (pci_has_subordinate(pdev)) pci_walk_bus(pdev->subordinate, pci_dev_set_disconnected, NULL); pci_stop_and_remove_bus_device(pdev); pci_dev_put(pdev); } result = reset_link(udev, severity); if (severity == AER_FATAL && dev->hdr_type == PCI_HEADER_TYPE_BRIDGE) { pci_walk_bus(dev->subordinate, report_resume, &result_data); pci_cleanup_aer_uncorrect_error_status(dev); dev->error_state = pci_channel_io_normal; } if (result == PCI_ERS_RESULT_RECOVERED) if (pcie_wait_for_link(udev, true)) pci_rescan_bus(udev->bus); pci_unlock_rescan_remove(); return result; } Regards, Oza.