Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1185410imm; Tue, 3 Jul 2018 07:01:37 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcNHG+vuJvcVC6Xvp3T2W3eEMc88bSOR9xlTH6zKVvIA1ByB3AEZ/t6QPn5FmhbSitmulty X-Received: by 2002:a62:3ece:: with SMTP id y75-v6mr21721831pfj.7.1530626497717; Tue, 03 Jul 2018 07:01:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530626497; cv=none; d=google.com; s=arc-20160816; b=irh4ZxhMXC701RVv3TNS9R2uOK8fiucMFAcvdfQFFi13//a/Km3YfKSQAxE9+tMViY D1peQ8Zpd9zEfJ+gxXVt6djr0+vezDxnIAWPGQkMXms2ux0TdEsRc3mcgt/OGJHHYY9I hx/2bx7peXnjQCGrkz1JThT+GnP5+qe5ymYc6+dCMf7sSXRgkTBjHssU7rBGQ1h0cOtP bGXdvmfbSmIoUoGBqTG7lxI8o4OOESjKl4XAah7h/agnwwDKjU+QEvi4s3HhcPwm9d0N 3ZOYSc+ShnzYXqaUxDN4pEpNaVvWY4BhrG2XpV7+llcTmauX2w/FgepwnvvyBug/Vycv wu5Q== 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:arc-authentication-results; bh=hzADDj5JUYkN5oFin57Yh9+sgSa0AvMYHe66ycX4MYY=; b=TRTSZZlNxSABU2r9evWvjTAFpNpE3Lt88g2comC8URIymqiFrxVecSo2l1iv88lxc/ xvohdPjI8OeKoY7hYMgfeCbyGlU7WNnxtMXSGbTI2+fnt0IeoUC+j2yZUm/NOG8NSoi4 S8U4CYGILWxNs4NvAJlnETQcMtnybKAHP7Na9gjZ3McE7hcOoEVHiNRjSV0BHSmhrjal 3ayP592EQmjh/2JtWnaQdf+JoOPZaqpk+6MDqBgJjDjJ7LWo5GkCk/eBp9Ka1m1gAWEm XDgoX9hscS2vj3CZodUAFtYvT8TF9m7siMOwSBCsZTs8pYBw9omH77HZwc/elTAxoSz4 gYpg== 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 x9-v6si1087564plo.368.2018.07.03.07.01.20; Tue, 03 Jul 2018 07:01:37 -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; 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 S932318AbeGCOAA (ORCPT + 99 others); Tue, 3 Jul 2018 10:00:00 -0400 Received: from bmailout3.hostsharing.net ([176.9.242.62]:58415 "EHLO bmailout3.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932219AbeGCN76 (ORCPT ); Tue, 3 Jul 2018 09:59:58 -0400 Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by bmailout3.hostsharing.net (Postfix) with ESMTPS id DEE18100E4168; Tue, 3 Jul 2018 15:59:56 +0200 (CEST) Received: by h08.hostsharing.net (Postfix, from userid 100393) id 8866B166A8; Tue, 3 Jul 2018 15:59:56 +0200 (CEST) Date: Tue, 3 Jul 2018 15:59:56 +0200 From: Lukas Wunner To: Sinan Kaya Cc: poza@codeaurora.org, linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Bjorn Helgaas , Keith Busch , open list Subject: Re: [PATCH V5 3/3] PCI: Mask and unmask hotplug interrupts during reset Message-ID: <20180703135956.GA18639@wunner.de> References: <1530571967-19099-1-git-send-email-okaya@codeaurora.org> <1530571967-19099-4-git-send-email-okaya@codeaurora.org> <20180703083447.GA2689@wunner.de> <8b6ce0f415858463d1c0588c29e30415@codeaurora.org> <9e871cc3978fbdca12ccf8a91f34ad07@codeaurora.org> <2640af5e-f00f-d814-425d-78ac57714f6d@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 03, 2018 at 09:31:24AM -0400, Sinan Kaya wrote: > Issue is observing hotplug link down event in the middle of AER recovery > as in my previous reply. > > If we mask hotplug interrupts before secondary bus reset via my patch, > then hotplug driver will not observe both link up and link down interrupts. > > If we don't mask hotplug interrupts, we have a race condition. I assume that a bus reset not only causes a link and presence event but also clears the Presence Detect State bit in the Slot Status register and the Data Link Layer Link Active bit in the Link Status register momentarily. pciehp may access those two bits concurrently to the AER driver performing a slot reset. So it may not be sufficient to mask the interrupt. I've posted this patch to address the issue: https://patchwork.ozlabs.org/patch/930391/ Thanks, Lukas