Received: by 10.223.185.116 with SMTP id b49csp7575185wrg; Thu, 1 Mar 2018 07:39:36 -0800 (PST) X-Google-Smtp-Source: AG47ELtgb7FL3mFzdTnvbJH6vgawRadupqIX3NNons2UBgOmKej0JZQgParNmmmOjrB2xA38BIRp X-Received: by 10.101.68.82 with SMTP id e18mr1857354pgq.329.1519918776770; Thu, 01 Mar 2018 07:39:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519918776; cv=none; d=google.com; s=arc-20160816; b=K8IAMj1gnMqQ4ApdOTH6a/avo+iDlq4gJHmmgcyE8VaTFdx8MpyD+2sBD50ZLz19a8 jeI8oY8LGx1A6rbt1v2v7v6cKTuIXFvU8t82W2Jx17q4ro6p6TlWAvhG7cdJA7LpA5O6 yd4AYQK7PbWLnR6WSkrVJMmsfu7z+3k/qlXOFbQhDyHKCs+Unyas8ZpZnkrnXcpNrCgs s3tTlAC6J60QFcZG6pbSpwG5iAZLmlOELBl6kyeXHEPuHl6mGbzkmMK3V8caTlnROL1q GWx/33X/uqCH+LZkxW+/97ZVldT/Qqqmadi/V6t0coxv4y5DqLZDTphEEr/wsk43hUkZ otzw== 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:dmarc-filter:arc-authentication-results; bh=yTSlMspq68DzprtlG2JJ+djWoyt+05wYTK6NCT3eu58=; b=XFF2aiwjKXYfcas+2dVRK22EJ4sjvMCqMdflX9MKHTq+cAOTOYngn2OB38A6s11jdt kdpi5ko8c9fU715teCW8FKGvLbKAbthDRhuXYY/Kyux7FOJJGMa3jNZjPqXn3Z6bfp2I ArYorHddqneQaEuatwyC5f1vQpSyXK0gXrTPS4U1Nz1YC5jH1iKW80gToCOZ5CZfRTgI bVamn08PEH/pSMMecRbwugmT5hSidjnNOwqavvt7GmMNMElcwuEEhSb54q9OOgPuDFgu d0CMsOQUn2rH7HTv700I2gVQf9gSjx663WToTjyAr0eFcw30oSrwrgwn/3gJ6fbjXNvL l5DQ== ARC-Authentication-Results: i=1; mx.google.com; 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 b9-v6si3146763pls.108.2018.03.01.07.39.21; Thu, 01 Mar 2018 07:39:36 -0800 (PST) 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; 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 S1032546AbeCAPiI (ORCPT + 99 others); Thu, 1 Mar 2018 10:38:08 -0500 Received: from mail.kernel.org ([198.145.29.99]:60720 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1032269AbeCAPiE (ORCPT ); Thu, 1 Mar 2018 10:38:04 -0500 Received: from localhost (50-81-63-165.client.mchsi.com [50.81.63.165]) (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 F3FB920685; Thu, 1 Mar 2018 15:38:03 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F3FB920685 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=helgaas@kernel.org Date: Thu, 1 Mar 2018 09:38:02 -0600 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] PCI/DPC: Fix INT legacy interrupt in dpc_irq Message-ID: <20180301153802.GD13722@bhelgaas-glaptop.roam.corp.google.com> References: <1517415535-21850-1-git-send-email-poza@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1517415535-21850-1-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 Hi Oza, On Wed, Jan 31, 2018 at 09:48:55PM +0530, Oza Pawandeep wrote: > Current dpc driver acknowledge the interrupt in deferred work, which works > okay since LPI are edge triggered. > But when RP does not have MSI support, port service driver falls back to > legacy GIC SPI interrupts, and with current code we do not acknowledge the > interrupt and we get dpc interrupt storm. > This patch acknowledges the interrupt in interrupt handler. Would you mind rephrasing this changelog in generic PCIe terms? E.g., "LPI" and "GIC SPI" are meaningless to me (I assume they're arm64-specific things), but I don't think it's any arm64-specific thing that motivates this change. IIUC, the issue should occur any time we're not using MSI, so we should be able to describe it in purely PCIe terms. s/dpc/DPC/ in text. It looks like this changelog is intended to be multiple paragraphs; if so, please leave a blank line between them. It's a little awkward to infer "this is a new paragraph" from the fact that "the previous line didn't look full" :) Please rebase to my "master" branch (v4.16-rc1). There was some minor change that made this not apply cleanly. > Signed-off-by: Oza Pawandeep > > diff --git a/drivers/pci/pcie/pcie-dpc.c b/drivers/pci/pcie/pcie-dpc.c > index 2d976a6..570b561 100644 > --- a/drivers/pci/pcie/pcie-dpc.c > +++ b/drivers/pci/pcie/pcie-dpc.c > @@ -134,7 +134,7 @@ static void interrupt_event_handler(struct work_struct *work) > } > > pci_write_config_word(pdev, dpc->cap_pos + PCI_EXP_DPC_STATUS, > - PCI_EXP_DPC_STATUS_TRIGGER | PCI_EXP_DPC_STATUS_INTERRUPT); > + PCI_EXP_DPC_STATUS_TRIGGER); > } > > static void dpc_rp_pio_print_tlp_header(struct device *dev, > @@ -277,6 +277,8 @@ static irqreturn_t dpc_irq(int irq, void *context) > > schedule_work(&dpc->work); > } > + pci_write_config_word(pdev, dpc->cap_pos + PCI_EXP_DPC_STATUS, > + PCI_EXP_DPC_STATUS_INTERRUPT); > return IRQ_HANDLED; > } > > -- > Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc., > a Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project. >