lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170608080017.GA12580@infradead.org>
Date:   Thu, 8 Jun 2017 01:00:17 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Alex Williamson <alex.williamson@...hat.com>
Cc:     kvm@...r.kernel.org, Jesse Brandeburg <jesse.brandeburg@...el.com>,
        Stefan Assmann <sassmann@...hat.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vfio/pci: Add Intel XXV710 to hidden INTx devices

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?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ