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]
Date:	Wed, 09 Nov 2011 17:43:39 -0700
From:	Myron Stowe <myron.stowe@...hat.com>
To:	jbarnes@...tuousgeek.org
Cc:	linux-pci@...r.kernel.org, bhelgaas@...gle.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] PCI: Convert maintaining FW-assigned BIOS BAR values to a
	list of temporary entries

In commit 58c84eda075 functionality was introduced that tries to reinstate
the original, FW-assigned, BAR addresses of a PCI device when normal
resource assignment attempts fail.  To keep track of the BIOS BAR
addresses, struct pci_dev was augmented with an array to hold the BAR
addresses of the PCI device: 'resource_size_t
fw_addr[DEVICE_COUNT_RESOURCE]'.

The reinstatement of BAR addresses is an uncommon event leaving the
'fw_addr' array unused normally.  As the use of struct pci_dev is so
prevalent, this seems wasteful.

This patch series introduces a stand alone data structure and
corresponding set of interfacing routines, converting the underlying
aspects of the existing maintanence scheme to a list of temporary BIOS
BAR value entries instead.

---

Myron Stowe (3):
      x86/PCI: Convert maintaining FW-assigned BIOS BAR values to use a list
      PCI: Maintain a list of FW-assigned BIOS BAR values
      PCI: Fix starting basis for resource requests


 arch/x86/pci/i386.c     |    2 -
 drivers/pci/setup-res.c |  100 ++++++++++++++++++++++++++++++++++++++++++-----
 include/linux/pci.h     |    2 -
 3 files changed, 92 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/

Powered by blists - more mailing lists