From: Christoph Hellwig <hch@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Stefan Assmann <sassmann@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfio/pci: Add Intel XXV710 to hidden INTx devices
Date: Thu, 8 Jun 2017 01:00:17 -0700 [thread overview]
Message-ID: <20170608080017.GA12580@infradead.org> (raw)
In-Reply-To: <20170607190132.22711.46831.stgit@gimli.home>
On Wed, Jun 07, 2017 at 01:01:46PM -0600, Alex Williamson wrote:
> XXV710 has the same broken INTx behavior as the rest of the X/XL710
> series, the interrupt status register is not wired to report pending
> INTx interrupts, thus we never associate the interrupt to the device.
> Extend the device IDs to include these so that we hide that the
> device supports INTx at all to the user.
Is vfio really the right place for the list? Shouldn't this be
keyed off the core PCI quirk for these devices?
next prev parent reply other threads:[~2017-06-08 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 19:01 [PATCH] vfio/pci: Add Intel XXV710 to hidden INTx devices Alex Williamson
2017-06-08 8:00 ` Christoph Hellwig [this message]
2017-06-08 13:06 ` Alex Williamson
2017-06-08 17:19 ` Jesse Brandeburg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170608080017.GA12580@infradead.org \
--to=hch@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sassmann@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox