Received: by 10.223.148.5 with SMTP id 5csp6220734wrq; Wed, 17 Jan 2018 10:50:36 -0800 (PST) X-Google-Smtp-Source: ACJfBosikMWg/x3dZgqP0+xDYfpZw3V1Ovryz31l2cKUNiV0Q8SglfmN30cPL3QKVFAZD5udb56p X-Received: by 10.84.214.130 with SMTP id j2mr32428459pli.339.1516215036734; Wed, 17 Jan 2018 10:50:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516215036; cv=none; d=google.com; s=arc-20160816; b=I217E6s2u+GfBgfPd9CuGR7r59g9S6rhxZFRtfRZISToy83ELH7F5W6sx9tORYj6mx APZyGPVDbHEooxUHQ0zi/F7MCGDqGf1ISJG+JpPfhsj2+alImc1imx6d8KoprHkldvDR CcCa2/sgSqOYU74DfxNogODt5kOs2+2Zrv2aP0UvwXhZig3mcJUa0IonG/FT09yrQeq5 HnCvWhVeEvKXHhjBs8z4M505W1/wi3RIcrxmxq+yo9AVC7w2QOx/IeAK4ikcuEAQ3IBt eXPRksVRv7GM1xEl+EMN/agc+J5jii6KHQsuJA5evkJpoSdvBTcJi4tlCPC6d0dMwKsw BHGQ== 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:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=i9cOBxB0El+3HL/EmsQ3dlydknqwcbzDTayYMjN4Kxs=; b=XhMxXY+kCKil94TinqcSUk2NVB9MfkS0ZvdVGKUbWZ4UEtJuckg4TxeVVwyXPP85G1 yyFOzi8KtNx11dNPe69o5yhvPJotpOsMhWp6aTtfgk770UI7VPnH66vIsgKTphw7wmz+ q/8HokOYbO0oyTRGEBWpMSV81AzEItx3rBMD/mB0w6vUxIGCxqvIHYGjJmQ3+yaMeixM 25ZSlvgDZVtxBC3vHlXvoOsfM/pdArAVfPyaGz9bcMswNZ0FnlsgdbbSwO9TRuV+1ZCS nqaTnbpBsx7ZUPiA/cq2lmmSfNl/6BVQi4d+nj+2anEeKEfD6c8H8FkCp6aHKkfAGLiH qdVg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 97si4980952plb.789.2018.01.17.10.50.21; Wed, 17 Jan 2018 10:50: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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754404AbeAQStq convert rfc822-to-8bit (ORCPT + 99 others); Wed, 17 Jan 2018 13:49:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:4154 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753950AbeAQStp (ORCPT ); Wed, 17 Jan 2018 13:49:45 -0500 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 414172C971F; Wed, 17 Jan 2018 18:49:45 +0000 (UTC) Received: from w520.home (ovpn04.gateway.prod.ext.phx2.redhat.com [10.5.9.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id BE10F63F94; Wed, 17 Jan 2018 18:49:44 +0000 (UTC) Date: Wed, 17 Jan 2018 11:49:44 -0700 From: Alex Williamson To: KarimAllah Ahmed Cc: linux-pci@vger.kernel.org, Bjorn Helgaas , linux-kernel@vger.kernel.org, "Jan H . =?UTF-8?B?U2Now7ZuaGVycg==?=" Subject: Re: [PATCH] pci: Do not read INTx PIN and LINE registers for virtual functions Message-ID: <20180117114944.4835c296@w520.home> In-Reply-To: <1516213829-14844-1-git-send-email-karahmed@amazon.de> References: <1516213829-14844-1-git-send-email-karahmed@amazon.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Wed, 17 Jan 2018 18:49:45 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 17 Jan 2018 19:30:29 +0100 KarimAllah Ahmed wrote: > ... since INTx is not supported by-spec for virtual functions. But the spec also states that VFs must implement the interrupt pin register as read-only zero, so either this is redundant or it's a workaround for VFs that aren't quite compliant? Thanks, Alex > > Cc: Bjorn Helgaas > Cc: linux-pci@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Signed-off-by: KarimAllah Ahmed > Signed-off-by: Jan H. Schönherr > --- > drivers/pci/probe.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c > index 65099d0..61002fb 100644 > --- a/drivers/pci/probe.c > +++ b/drivers/pci/probe.c > @@ -1232,6 +1232,13 @@ static void pci_read_irq(struct pci_dev *dev) > { > unsigned char irq; > > + /* Virtual functions do not have INTx support */ > + if (dev->is_virtfn) { > + dev->pin = 0; > + dev->irq = 0; > + return; > + } > + > pci_read_config_byte(dev, PCI_INTERRUPT_PIN, &irq); > dev->pin = irq; > if (irq)