linux-kernel - [PATCH 0/2] PCI: Don't enable realloc automatically when above 4g 64bit mmio is not supported

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: <1386546869-31900-1-git-send-email-yinghai@kernel.org>
Date:	Sun,  8 Dec 2013 15:54:27 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Joseph Salisbury <joseph.salisbury@...onical.com>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	Yinghai Lu <yinghai@...nel.org>
Subject: [PATCH 0/2] PCI: Don't enable realloc automatically when above 4g 64bit mmio is not supported

On one system (Dell) realloc auto cause ixgbe does not work,
the system does not have enough range for sriov and rom.

We could try to tighten the condition about enabling realloc auto.
Not enabling realloc auto when above 64bit mmio is not there for
root bus.
So the system does not need to take "pci=realloc=off" to have working
network as old kernel.

First patch is preparing for bus address converting with bus instead of dev.

After those two patches get into pci-next or linus-tree, I will send
other patches about 64bit resource allocation.

Thanks

Yinghai

Yinghai Lu (2):
  PCI: pcibus address to resource converting take bus instead of dev
  PCI: Only enable realloc auto when root bus has 64bit mmio

 drivers/pci/host-bridge.c | 34 +++++++++++++++++++++-------------
 drivers/pci/setup-bus.c   | 32 +++++++++++++++++++++++++++-----
 include/linux/pci.h       |  5 +++++
 3 files changed, 53 insertions(+), 18 deletions(-)

-- 
1.8.4

--
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/