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] [day] [month] [year] [list]
Date:   Mon, 13 Mar 2017 13:55:04 -0500
From:   Bjorn Helgaas <>
To:     Mason <>
Cc:     linux-pci <>,
        David Laight <>,
        Robin Murphy <>,
        Thibaud Cornic <>,
        Phuong Nguyen <>,
        Linux ARM <>,
        netdev <>,
        Tim Harvey <>,
        Arnd Bergmann <>
Subject: Re: Legacy features in PCI Express devices

On Mon, Mar 13, 2017 at 05:10:57PM +0100, Mason wrote:
> Hello,
> There are two revisions of our PCI Express controller.
> Rev 1 did not support the following features:
>   1) legacy PCI interrupt delivery (INTx signals)
>   2) I/O address space
> Internally, someone stated that such missing support would prevent
> some PCIe cards from working with our controller.
> Are there really modern PCIe cards that require 1) and/or 2)
> to function?

>From a spec point of view, all endpoints, including Legacy, PCI
Express, and Root Complex Integrated Endpoints, are "required to
support MSI or MSI-X or both if an interrupt resource is requested"
(PCIe r3.0, sec 1.3.2).

The same section says Legacy Endpoints are permitted to use I/O
Requests, but PCI Express and Root Complex Integrated Endpoints are
not.  There's a little wiggle room in the I/O BAR description; I would
interpret it to mean the latter two varieties are permitted to have
I/O BARs, but they must make the resources described by those BARs
available via a memory BAR as well, so they can operate with I/O
address space.

But that's only in theory; David has already given examples of devices
that don't support MSI, and Greg hinted at new devices that might
require I/O space.  I'm particularly curious about that last one,
because there are several host bridges that don't support I/O space at


Powered by blists - more mailing lists