From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3B7EFC433F4 for ; Fri, 21 Sep 2018 15:16:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E727021532 for ; Fri, 21 Sep 2018 15:16:20 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E727021532 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390612AbeIUVFi (ORCPT ); Fri, 21 Sep 2018 17:05:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41344 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390371AbeIUVFi (ORCPT ); Fri, 21 Sep 2018 17:05:38 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 83C3686663; Fri, 21 Sep 2018 15:16:18 +0000 (UTC) Received: from t450s.home (ovpn-116-77.phx2.redhat.com [10.3.116.77]) by smtp.corp.redhat.com (Postfix) with ESMTP id C3ADE7FFF1; Fri, 21 Sep 2018 15:16:17 +0000 (UTC) Date: Fri, 21 Sep 2018 09:16:17 -0600 From: Alex Williamson To: Christoph Hellwig Cc: kvm@vger.kernel.org, ashok.raj@intel.com, gage.eads@intel.com, gnomes@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] vfio/pci: Mask buggy SR-IOV VF INTx support Message-ID: <20180921091617.07a96af5@t450s.home> In-Reply-To: <20180921055304.GA12584@infradead.org> References: <153747346143.7344.14634545723456004489.stgit@gimli.home> <20180921055304.GA12584@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Fri, 21 Sep 2018 15:16:18 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 20 Sep 2018 22:53:04 -0700 Christoph Hellwig wrote: > > +/* > > + * Nag about hardware bugs, hopefully to have vendors fix them, but at least > > + * to collect a list of dependencies for the VF INTx pin quirk below. > > + */ > > +static const struct pci_device_id known_bogus_vf_intx_pin[] = { > > + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x270c) }, > > + {} > > +}; > > What device is this? We don't have the device ID anywhere, so I guess > it is something match by the class code? Intel hasn't disclosed the device yet, so we don't know that there's an existing driver at all for it. Thanks, Alex