linux-kernel - [PATCH v2 0/2] ACPI / PCI: Fix _PRT lookup for ARI enabled devices

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-next>] [day] [month] [year] [list]

Message-ID: <20150526210927.7537.55656.stgit@gimli.home>
Date:	Tue, 26 May 2015 15:11:38 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org
Cc:	bhelgaas@...gle.com, ddutile@...hat.com, rjw@...ysocki.net,
	linux-kernel@...r.kernel.org, lenb@...nel.org
Subject: [PATCH v2 0/2] ACPI / PCI: Fix _PRT lookup for ARI enabled devices

v2: don't modify entry->id.device

In most cases we only use ARI with SR-IOV VFs, which do not support
INTx and therefore never hit this problem.  However, some non-SR-IOV
implementations create multiple PFs, extending beyond the standard
3-bit function numbers with ARI, and do support INTx for those
additional functions.  This can happen with Solarflare SFC9120
adapters.  The host driver typically doesn't use INTx, so we also
haven't noticed this problem on bare metal, but when we attempt to
assign the device to a VM using vfio-pci, we fail trying to setup
default INTx signaling.  Thanks,

Alex

---

Alex Williamson (2):
      PCI: Move pci_ari_enabled() to global header
      ACPI / PCI: Account for ARI in _PRT lookups

 drivers/acpi/pci_irq.c |    2 +-
 drivers/pci/pci.h      |   11 -----------
 include/linux/pci.h    |   11 +++++++++++
 3 files changed, 12 insertions(+), 12 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/