Received: by 10.192.165.156 with SMTP id m28csp320504imm; Mon, 16 Apr 2018 00:07:27 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+Pi9METOUCaqCBXyoz8lcA2SMR1BRaKmitUqchqQyFNxRiSe7wn5R9ERdNw7KF82/qK4tW X-Received: by 10.98.171.7 with SMTP id p7mr20481508pff.215.1523862447752; Mon, 16 Apr 2018 00:07:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523862447; cv=none; d=google.com; s=arc-20160816; b=IJ3sXtAnkKgN4nBGVizXvc7TPbkm1MiCOcmSQ8rEpEkb5/wcgKLr6nYJZ6vrYYXNzr 0Q94KrR7Wb6Ct0mPXI3O0RY/bKzhw7QSV5gv2fJc1ySRuDbYHbvazXIk/zNZEuNSh+9G lUHJcPadGCAwUKdrXZehoanA952XBrl40oVLeLx2yVKNxQeVtANidMCgbYlUNEyPvovW 6UoveHLitlVWn0vWIctQ7jb+tBLIDfVzOF+gCuU68PMkmYUeu+dpxXkN9OufV40ciyj7 Zv+NdFrDN4WE6j02tjI4gE9PH6nwaB+19rKvtLElOfVZSTgBDwm8mZS1cO0WR0jkQNs7 h2nQ== 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=toFoDYF1N7ONODP8U/238uLqZvqpvz6SDoTGQ2QcR0w=; b=r3eUR79uebdWOjC0AfToWQ0j6RhobIB87/62EvSY5f7E4kLl/Ip2trkbL/UQue6jEB eRN/CC9XhOpiYXDcbeuzhwkmMd/hrrMKvmW95u/g4GZTCe8i4wpnLmMXP5JX6XG6VX2k vz44XDOvNwQ/l8siuIJ4ef7/+SbkvM6LRhXq6gjTelGWs+h1Mf4rrMxT/0h8Ytw0APbK TA8nsfJ7wxDB+OL9KRik4VhEp/fU9z06Icp107Cn5lAxb3FWdZAcFBqew+tBGlLgWSQN Xv+IkoTDTAShl7Q2RcnUpUW2VGb8pacIfEtbhMg7+NlcqnIK/ffDK1PANRi1EJNZSuqT YZjQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=QfSP1JKL; dkim=pass header.i=@codeaurora.org header.s=default header.b=eX+9P120; 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 p1-v6si11266751plb.355.2018.04.16.00.07.11; Mon, 16 Apr 2018 00:07:27 -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=QfSP1JKL; dkim=pass header.i=@codeaurora.org header.s=default header.b=eX+9P120; 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 S1753244AbeDPGDQ (ORCPT + 99 others); Mon, 16 Apr 2018 02:03:16 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:44154 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753215AbeDPGDO (ORCPT ); Mon, 16 Apr 2018 02:03:14 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 217B360C64; Mon, 16 Apr 2018 06:03:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1523858594; bh=a76diAHWopdpuayZNBaaUn4OwCDEJB+uX5HP5AIcEJs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=QfSP1JKLdsnNnJkkQ1OMtf7i8cE5sKwlFjJDFtSMu2Izgqxw91I2wgaJ7rwwdhMdB HXsctCB1Uh1DQcmaE1qeQQyfF2KgG+PSzLZJeatLId/yZZqH+45dQQDbzOdDXBEgPR ZAEb8dVrlkxwMvwX/9d/i4kJ2UN5oadiNYYFez8o= 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 4E40960500; Mon, 16 Apr 2018 06:03:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1523858593; bh=a76diAHWopdpuayZNBaaUn4OwCDEJB+uX5HP5AIcEJs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=eX+9P120E6KDIE2YSEbu+UD69mo6tEmUdyWu4fHLeu4bSHPEPPJbNar7CL+3Xjogj bUu7QHvTp+4UOdtEv7jEG2WP+JJ9EGj3uCkOOB9eguaP/m2ng1XYzVmijb1ERrlsaW mIDgHkENvrqLm0QaMgd9IQeYZdxX4bQwoOH+GOBg= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 16 Apr 2018 11:33:13 +0530 From: poza@codeaurora.org To: Sinan Kaya Cc: Bjorn Helgaas , 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 , Timur Tabi Subject: Re: [PATCH v13 0/6] Address error and recovery for AER and DPC In-Reply-To: <5b4e667f-bead-a007-78dd-e42d3194f232@codeaurora.org> References: <1523284914-2037-1-git-send-email-poza@codeaurora.org> <20180416031600.GB80087@bhelgaas-glaptop.roam.corp.google.com> <5b4e667f-bead-a007-78dd-e42d3194f232@codeaurora.org> Message-ID: <9301606a70a213c180d9e6764b002cf9@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-04-16 09:23, Sinan Kaya wrote: > On 4/15/2018 11:16 PM, Bjorn Helgaas wrote: >> On Mon, Apr 09, 2018 at 10:41:48AM -0400, 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. >>> >>> DPC should behave identical to AER as far as error handling is >>> concerned. >>> DPC should remove the devices and not to do recovery for hotplug >>> enabled system. >> >> Is there a specific bug that's fixed by these patches? I didn't see >> one mentioned in the changelogs. >> > > There is no actual bug. > > We realized that DPC and hotplug is heavily integrated today. We have > use > cases for systems without hotplug support but still support DPC. That's > the > problem we are trying to solve with this patchset. Adding to what Sinan said; 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. It achieves uniformity and transparency to the error handling agents such as AER, DPC, with respect to recovery and error handling. So, this patch-set tries to unify lot of things between error agents and make them behave in a well defined way. (be it error (FATAL, NON_FATAL) handling or recovery). Regards, Oza.