Received: by 10.192.165.148 with SMTP id m20csp4744358imm; Tue, 1 May 2018 03:02:32 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoat4HEfpCxMFe6fdqnIZNYkUk6/QNG/xv8HXVBjUiAIjZi/73r3rdzCLCNeRQipO7hHdyQ X-Received: by 2002:a63:6842:: with SMTP id d63-v6mr12593505pgc.304.1525168952764; Tue, 01 May 2018 03:02:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525168952; cv=none; d=google.com; s=arc-20160816; b=BTQaFuZ26OOaRRQSdpUZLGjyQEoVhgHQJmOCKJY0ZD+yTghTYIwwRDiq/P3D2VvC0Q KQkTIQUGZC9C6zbFilIdiPrZR1/VW4A+uD5PzktmZOKlcDgHdkYMqjqnOae+JutDOBYc zik+ijxCF14ow93EunAPqQ1HoQRff5AG1GMYLBxFskb/39sRAI6OZh0SyOpGoSrxKHHR ogU2DMGTcFawHhMlEQU9Ei1s9+2BHeIIU4wZ7jQf4/IwycQnrvB5p/uPLQlaDn/v9sI5 MjH4LpE9sVvrnkEOIuYzbBXDSpb4hq/q2rubn699Hh4KkAX8iKOArzk3KTZtwxMaK+XS YZ4Q== 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=H1ZoAAzOjPRA/nG8HmB+jULNXpLl+95gL+ItcPbyd8E=; b=YYZk+hD45AKnDYBhztEDeIcz9tt6vQO3DgNLXDPXIoqtr+wwl+aGtMcAr3rT8rM7yB Hnyiau5bv/BUSlXOh/s1ZFTONn7COiKyE1y+M2ovQjvxTHclhMCpz0lCL8IQde/acw1o DefymF3b5ESWJGCRkovbhNfh9WuWrGsrvdxZq/0vQy8zPuxO9i0GaQaBJiAO+EsHR99A 48nLjZt7AodeqyccAUdXc1jkKn3K1190l+rejlkN66Gh/m++Viektm97YSQ/HdwC/xqj rKs2DMsgdpo5s/8R/fggPUJAVnY1UNv8wWKzWnwlavNHrnKCgnuOhLCXOUM35WfHYWx7 vePw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=QpyjgDT2; dkim=pass header.i=@codeaurora.org header.s=default header.b=bw+XJ4Ry; 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 w61-v6si9089994plb.155.2018.05.01.03.02.18; Tue, 01 May 2018 03:02: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=QpyjgDT2; dkim=pass header.i=@codeaurora.org header.s=default header.b=bw+XJ4Ry; 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 S1754015AbeEAKBB (ORCPT + 99 others); Tue, 1 May 2018 06:01:01 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:39382 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751090AbeEAKA6 (ORCPT ); Tue, 1 May 2018 06:00:58 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 494466090E; Tue, 1 May 2018 10:00:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525168858; bh=7swzCSRkw4BV0EpGepV38L3YiuFzwLARIjM0p4Uqtzc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=QpyjgDT2U9Ma0dLu6M2CtHvN7Xuc0I4D6kDPaEXYbZv+2+K32/2eJSeF6eCQZFKTD MD7WQvLX/7v9c/RV2y6aLsqq91Jw8J48s/d471qkrCQP2NV68j3d64CIgiMQFqIlAz JzoMV7qXyCx+QDKK9WNuJogEulrYu24B21FwTuDQ= 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 2B19860588; Tue, 1 May 2018 10:00:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525168857; bh=7swzCSRkw4BV0EpGepV38L3YiuFzwLARIjM0p4Uqtzc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=bw+XJ4RyEJHz6mvBmpm7OWPo/ySDBvGOY+rJzcTRW/XVQtvSMTNuYf6iFBQgAX6MP T+2jTzFdEO9Zh9KwQzmJVkelpAD8RLoSpoLAV3LWkjTzZLryZqLprhwJ0WuKPNui+f dz/T4aS/PHPwXBvhpqSBnhz280jl4uL7RRGRzJ1M= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 01 May 2018 15:30:57 +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 Subject: Re: [PATCH v14 0/9] Address error and recovery for AER and DPC In-Reply-To: <20180430224002.GI95643@bhelgaas-glaptop.roam.corp.google.com> References: <1524496993-29799-1-git-send-email-poza@codeaurora.org> <20180430224002.GI95643@bhelgaas-glaptop.roam.corp.google.com> Message-ID: <42d49b12f1465d6d6c2fdfd182031881@codeaurora.org> 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-01 04:10, Bjorn Helgaas wrote: > On Thu, Apr 26, 2018 at 11:00:52AM +0530, poza@codeaurora.org wrote: >> On 2018-04-23 20:53, Oza Pawandeep wrote: >> > This patch set brings in error handling support for DPC >> > >> > The current implementation of AER and error message broadcasting to the >> > EP driver is tightly coupled and limited to AER service driver. >> > It is important to factor out broadcasting and other link handling >> > callbacks. So that not only when AER gets triggered, but also when DPC >> > get >> > triggered (for e.g. ERR_FATAL), callbacks are handled appropriately. >> > >> > The goal of the patch-set is: >> > DPC should handle the error handling and recovery similar to AER, >> > because >> > finally both are attempting recovery in some or the other way, >> > and for that error handling and recovery framework has to be loosely >> > coupled. >> > ... > >> Hi Bjorn, >> >> I know I need to rebase this whole patch-set to 4.17 now. >> >> But before I do that, can you please help to comment. > > My overall comment is that I think the series will be simpler and read > better if you first change AER to do remove/re-enumerate, before doing > anything with DPC. > > This could be done by extracting just the AER part of "PCI/AER/DPC: > Align FATAL error handling for AER and DPC" (i.e., adding > pcie_do_fatal_recovery()) and moving that to be the very first patch. > > It's a small change in terms of code size, but significant to drivers, > and it's really the core of the series, so it would be good to clearly > establish the policy of: > > ERR_NONFATAL => call driver recovery entry points > ERR_FATAL => remove and re-enumerate > > before bringing DPC into the picture. > > Then the subsequent patches would all be more or less mechanical > changes to make DPC follow the same model. ok I have taken care of you comment, please follow v15, coming next. I could not make that the first patch, because I needed to unify pci_wait_for_link function. hence it is the second patch, but now the order looks quiet obvious and simplified. Regards, Oza. > > Bjorn