Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp1269056imm; Tue, 15 May 2018 17:00:26 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpu7W7+xoTuOZ25SNFZlVTMLlp8usPec8WHFJdH8ybq5zq02Xa1O0EiHaPEMGVHohXWToHl X-Received: by 2002:a62:9b57:: with SMTP id r84-v6mr17264003pfd.109.1526428826034; Tue, 15 May 2018 17:00:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526428826; cv=none; d=google.com; s=arc-20160816; b=InY0HlTsmjSKnLCMykwwGzzFnaoLLy9NtCmv3YGkPrZeuW2woYO10AYFriVSYry0Xu ReDaDdN75WKp8KYc1+x48RRzTrNRiiiz5674kBrNhDCestjulUQmLt6PzH1Ly6A1aahN bwbRW9XUjmsg3e1fUfRbhUEqwk/fcJ8vWWUP05ss9ezCKz0Gc4lyOeTw2o/lMzDaBChc TY/x310awuP5nueze0V+WQXY/UiyQEOUq7/9Yzy69YjVSDFbslklO3aIUFbCGkP6S2a6 mnu7SDi5h8lMloyhIPqXC6dYzmcC4lwewf0YHv/JSRxVRfySHaGDjeMxDibJyOuXgWH9 1Cuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=nAkYN3LwwVYVDlaBfg+3X0Z/xGkE+X/G4q+h8bNyIag=; b=WTQErH9eotAjVfwdi53jbbOiIfjnBPPK9/iTWJbO+akQ+gcmAo0OzBwshxZnOQJaJt 0uMrsSNZGIeZMSN/uuu8iW7aCxAkPQnnCTvcsjWkpeJF08oM9g4PlDolrqY0tGTphQ// G5dFag3RA64FXByP5jHFxtzn3G2/k+KuaGO8Sj3aYA0Pl+vsw8/9MzXLsJhJJrrp/Jko OrTvjy7lZdo6CT2MYHpTxfix2DV0MeWvmvYF6xoMN5a+Lv+aV5WdyQ7Ua07hM08+o0cH cs1UjyTMMx83AfG3bQ6dAGjTRqJthmbOflW56Zf2y5Xu1nWVZzxBBw7iZDH1kVkMTbZh QrFw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ig9+Xdaq; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a35-v6si1101347pli.85.2018.05.15.17.00.11; Tue, 15 May 2018 17:00:25 -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=@kernel.org header.s=default header.b=ig9+Xdaq; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752265AbeEOX74 (ORCPT + 99 others); Tue, 15 May 2018 19:59:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:49142 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751400AbeEOX7z (ORCPT ); Tue, 15 May 2018 19:59:55 -0400 Received: from localhost (unknown [69.71.5.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5012A20657; Tue, 15 May 2018 23:59:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1526428794; bh=6H3ySFivAPvZrDHFo/egLl9wC2jMhOBkINI9ayPyRrY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ig9+XdaqQ5yK1EFIfWmjV5iaOrwrOLeiC7J0rcCWMuF9FsZhHe6Mgiiv7LTOu5zGZ oN4rD74bhkN5MA/hVCaMPVkzzojVFzwlMPwKXuZVI9dKEJYAGQmdQkdBlFVb1b7g/5 jaRCSQbZLUOrMVkf+7oljcL9nVjE6fhVI2VpkUgw= Date: Tue, 15 May 2018 18:59:52 -0500 From: Bjorn Helgaas To: Oza Pawandeep 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 Subject: Re: [PATCH v16 3/9] PCI/AER: Handle ERR_FATAL with removal and re-enumeration of devices Message-ID: <20180515235952.GC11156@bhelgaas-glaptop.roam.corp.google.com> References: <1526035408-31328-1-git-send-email-poza@codeaurora.org> <1526035408-31328-4-git-send-email-poza@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1526035408-31328-4-git-send-email-poza@codeaurora.org> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 11, 2018 at 06:43:22AM -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 > Reviewed-by: Keith Busch > > diff --git a/drivers/pci/pcie/aer/aerdrv_core.c b/drivers/pci/pcie/aer/aerdrv_core.c > index 0ea5acc..649dd1f 100644 > --- a/drivers/pci/pcie/aer/aerdrv_core.c > +++ b/drivers/pci/pcie/aer/aerdrv_core.c > @@ -20,6 +20,7 @@ > #include > #include > #include "aerdrv.h" > +#include "../../pci.h" > > #define PCI_EXP_AER_FLAGS (PCI_EXP_DEVCTL_CERE | PCI_EXP_DEVCTL_NFERE | \ > PCI_EXP_DEVCTL_FERE | PCI_EXP_DEVCTL_URRE) > @@ -475,35 +476,84 @@ static pci_ers_result_t reset_link(struct pci_dev *dev) > } > > /** > - * do_recovery - handle nonfatal/fatal error recovery process > + * do_fatal_recovery - handle fatal error recovery process > + * @dev: pointer to a pci_dev data structure of agent detecting an error > + * > + * Invoked when an error is fatal. Once being invoked, removes the devices > + * benetah this AER agent, followed by reset link e.g. secondary bus reset > + * followed by re-enumeration of devices. > + */ > + > +static void do_fatal_recovery(struct pci_dev *dev) > +{ > + struct pci_dev *udev; > + struct pci_bus *parent; > + struct pci_dev *pdev, *temp; > + pci_ers_result_t result = PCI_ERS_RESULT_RECOVERED; > + struct aer_broadcast_data result_data; > + > + 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); I don't like the fact that for DPC, the link reset happens before we call the driver .remove() methods, while for AER, the reset happens *after* the .remove() methods. That means the .remove() methods may work differently for AER vs. DPC, e.g., they may be able to access the device if AER is handling the error, but they would not be able to access it if DPC is handling it. I don't know how to fix this, and I think we can keep this patch as it is for now, but I think we should fix it eventually. > + if (dev->hdr_type == PCI_HEADER_TYPE_BRIDGE) { > + /* > + * If the error is reported by a bridge, we think this error > + * is related to the downstream link of the bridge, so we > + * do error recovery on all subordinates of the bridge instead > + * of the bridge and clear the error status of the bridge. > + */ > + pci_walk_bus(dev->subordinate, report_resume, &result_data); > + pci_cleanup_aer_uncorrect_error_status(dev); > + } > + > + if (result == PCI_ERS_RESULT_RECOVERED) { > + if (pcie_wait_for_link(udev, true)) > + pci_rescan_bus(udev->bus); > + } else { > + pci_uevent_ers(dev, PCI_ERS_RESULT_DISCONNECT); > + pci_info(dev, "AER: Device recovery failed\n"); > + } > + > + pci_unlock_rescan_remove(); > +} > + > +/** > + * do_nonfatal_recovery - handle nonfatal error recovery process > * @dev: pointer to a pci_dev data structure of agent detecting an error > - * @severity: error severity type > * > * Invoked when an error is nonfatal/fatal. Once being invoked, broadcast > * error detected message to all downstream drivers within a hierarchy in > * question and return the returned code. > */ > -static void do_recovery(struct pci_dev *dev, int severity) > +static void do_nonfatal_recovery(struct pci_dev *dev) > { > - pci_ers_result_t status, result = PCI_ERS_RESULT_RECOVERED; > + pci_ers_result_t status; > enum pci_channel_state state; > > - if (severity == AER_FATAL) > - state = pci_channel_io_frozen; > - else > - state = pci_channel_io_normal; > + state = pci_channel_io_normal; > > status = broadcast_error_message(dev, > state, > "error_detected", > report_error_detected); > > - if (severity == AER_FATAL) { > - result = reset_link(dev); > - if (result != PCI_ERS_RESULT_RECOVERED) > - goto failed; > - } > - > if (status == PCI_ERS_RESULT_CAN_RECOVER) > status = broadcast_error_message(dev, > state, > @@ -562,8 +612,10 @@ static void handle_error_source(struct pcie_device *aerdev, > if (pos) > pci_write_config_dword(dev, pos + PCI_ERR_COR_STATUS, > info->status); > - } else > - do_recovery(dev, info->severity); > + } else if (info->severity == AER_NONFATAL) > + do_nonfatal_recovery(dev); > + else if (info->severity == AER_FATAL) > + do_fatal_recovery(dev); > } > > #ifdef CONFIG_ACPI_APEI_PCIEAER > @@ -627,8 +679,10 @@ static void aer_recover_work_func(struct work_struct *work) > continue; > } > cper_print_aer(pdev, entry.severity, entry.regs); > - if (entry.severity != AER_CORRECTABLE) > - do_recovery(pdev, entry.severity); > + if (entry.severity == AER_NONFATAL) > + do_nonfatal_recovery(pdev); > + else if (entry.severity == AER_FATAL) > + do_fatal_recovery(pdev); > pci_dev_put(pdev); > } > } > -- > 2.7.4 >