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;
Date:   Fri, 21 Sep 2018 09:16:17 -0600
From:   Alex Williamson <alex.williamson@redhat.com>
To:     Christoph Hellwig <hch@infradead.org>
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
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 20 Sep 2018 22:53:04 -0700
Christoph Hellwig <hch@infradead.org> 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