Received: by 10.192.165.156 with SMTP id m28csp726581imm; Mon, 16 Apr 2018 07:47:28 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+CHvIbI2ti1cUHZRdmTWtayMYNiRs3mrdsEfA4HEJd+7XOWYU+K5bn5mtdnCOdI1+HeBXp X-Received: by 10.99.0.148 with SMTP id 142mr7993408pga.227.1523890048072; Mon, 16 Apr 2018 07:47:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523890048; cv=none; d=google.com; s=arc-20160816; b=g+Nl47zIhXyHFBs/aGj+vtrZowbrvXGE4WxQlDWKhNEr0zmJhmlzDizhbLcIkI61G0 jdObOY46H0MP3XYBV/J9+6dN6theMdxnhyw4jefOzQlm3iB5o7ViuxwPnY1ENjbNJgHx x/TS40JFVRWYu6JaqzIZSqAfq3UzJ49FoC2gkoCuCg1J+RgF1Z7G604Iou5WNskdyzZC 0McBnlX76/uFXVXJyWbRMya52r8O9eNCum13LBZkFaZ9V2iPCL3WEuf/As1b0QzInP6v BJwXXW7/MqSAedHYXsCzkGMfeV0l5gyDiaGO44AkKfIs9iG6TUA2gFXflY/UlZdqj/F9 eEYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dmarc-filter :dkim-signature:dkim-signature:arc-authentication-results; bh=vGq3Xl49xNHG7T/nuxkuVYk6MWk2SSP8NGWP69p3hD4=; b=k6FLDpUWRYW/ADPRDByVx8xBZrisyVuma8VotiaUeYnhWnDynaaUDn3FHzFJ70ekfs tl9Y4yjZGt8UnXrjtNBoN73tDiV1IUzVMiDv97j/3Qjq0LbFaiN3cfDM5/qUvcWqfhjI bBBtVrsMfFCDV++vtpfcQzJMbmk7nNZ41nxRlo1InnW6swZpptYvOQgpKswKDgtg+Eno hhapM6K5ddJlZyF5MsZYuuSqdyD+44eoIvBsbz3B1KtXAZz5027/ePLDZm1/haDCmKan e876iFpAgfiFniDrYiofFtX3rpt/K2EJeJJDzgfZ5mqIXExikqLTjgcAzgNKsKFJ9gyP XHVw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=cRoTCCF1; dkim=pass header.i=@codeaurora.org header.s=default header.b=QSpI9byu; 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 c2si746980pgw.613.2018.04.16.07.47.14; Mon, 16 Apr 2018 07:47:28 -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=cRoTCCF1; dkim=pass header.i=@codeaurora.org header.s=default header.b=QSpI9byu; 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 S1751149AbeDPOqM (ORCPT + 99 others); Mon, 16 Apr 2018 10:46:12 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:33594 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750708AbeDPOqK (ORCPT ); Mon, 16 Apr 2018 10:46:10 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 15E71601E6; Mon, 16 Apr 2018 14:46:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1523889970; bh=2NbICc8/rtGudp9UI2snHLCKYr9ok5W5garP+b03W3g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=cRoTCCF1z5gTKrsdVDVMxk3MG5YoxccGARkSfzvaDd+0qWxu2eMMRg16rFUF8YqBp vc8l536SZ0AaO/dMoMnw2UxG0/3PbhzsMrnhI/hqAkBQWkBQ/2MGO6rvfMU9xnqcU/ epW1gYuOfcPGe4f5LV59qzpsBYbnSonPgoyZrRCE= 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 [10.235.228.150] (global_nat1_iad_fw.qualcomm.com [129.46.232.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: okaya@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 9162A60AE0; Mon, 16 Apr 2018 14:46:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1523889968; bh=2NbICc8/rtGudp9UI2snHLCKYr9ok5W5garP+b03W3g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=QSpI9byu/OKnqGq0ch6YBOO33ym/8txzkHKuKdNbOEz3TDlK6Y+Kg5OV8PZsj9zJY nW7MQkBGdr14LoOP8UX1ZI1MR9DsF2t1LWGfxAT1mskTzfOqUMpyESTIAzTd9qZb4q Uev5LcbZ7WUI5GniMtZ4GkubvKa5LFSU1u8kdOcU= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 9162A60AE0 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=okaya@codeaurora.org Subject: Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system To: Bjorn Helgaas Cc: Keith Busch , Oza Pawandeep , Bjorn Helgaas , Philippe Ombredanne , Thomas Gleixner , Greg Kroah-Hartman , Kate Stewart , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Dongdong Liu , Wei Zhang , Timur Tabi , Alex Williamson References: <20180410210349.GG54986@bhelgaas-glaptop.roam.corp.google.com> <13efe2e8-74c8-acb4-ec58-f79b14a1f182@codeaurora.org> <20180412140648.GD145698@bhelgaas-glaptop.roam.corp.google.com> <20180412143954.GB4810@localhost.localdomain> <20180412150231.GD4810@localhost.localdomain> <20180412170911.GA6424@localhost.localdomain> <20180416031726.GB158153@bhelgaas-glaptop.roam.corp.google.com> From: Sinan Kaya Message-ID: Date: Mon, 16 Apr 2018 10:46:04 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180416031726.GB158153@bhelgaas-glaptop.roam.corp.google.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/15/2018 11:17 PM, Bjorn Helgaas wrote: > It doesn't seem right to me that we handle both ERR_NONFATAL and > ERR_FATAL events differently if we happen to have DPC support in a > switch. > > Maybe we should consider triggering DPC only on ERR_FATAL? That would > keep DPC out of the ERR_NONFATAL cases. > From reliability perspective, it makes sense. DPC handles NONFATAL errors by bringing down the link. If error happened behind a switch and root port is handling DPC, we are impacting a lot of devices operation because of one faulty device. Keith, do you have any preference on this direction? > For ERR_FATAL, maybe we should bite the bullet and use > remove/re-enumerate for AER as well as for DPC. That would be painful > for higher-level software, but if we're willing to accept that pain > for new systems that support DPC, maybe life would be better overall > if it worked the same way on systems without DPC? Sure, we can go to this route as well. -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.