<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/pci, branch v3.1.7</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/pci?h=v3.1.7</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/pci?h=v3.1.7'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-12-09T16:54:08Z</updated>
<entry>
<title>PCI hotplug: shpchp: don't blindly claim non-AMD 0x7450 device IDs</title>
<updated>2011-12-09T16:54:08Z</updated>
<author>
<name>Bjorn Helgaas</name>
<email>bhelgaas@google.com</email>
</author>
<published>2011-08-23T16:16:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=14855077253713109f8a835cc6e9271432460de9'/>
<id>urn:sha1:14855077253713109f8a835cc6e9271432460de9</id>
<content type='text'>
commit 4cac2eb158c6da0c761689345c6cc5df788a6292 upstream.

Previously we claimed device ID 0x7450, regardless of the vendor, which is
clearly wrong.  Now we'll claim that device ID only for AMD.

I suspect this was just a typo in the original code, but it's possible this
change will break shpchp on non-7450 AMD bridges.  If so, we'll have to fix
them as we find them.

Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638863
Reported-by: Ralf Jung &lt;ralfjung-e@gmx.de&gt;
Cc: Joerg Roedel &lt;joerg.roedel@amd.com&gt;
Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;
Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>xen-pcifront: Update warning comment to use 'e820_host' option.</title>
<updated>2011-11-11T17:42:48Z</updated>
<author>
<name>Konrad Rzeszutek Wilk</name>
<email>konrad.wilk@oracle.com</email>
</author>
<published>2011-07-22T16:18:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6d473ffdabc38ccad26986f61a2e10fd487bb86d'/>
<id>urn:sha1:6d473ffdabc38ccad26986f61a2e10fd487bb86d</id>
<content type='text'>
commit 917e3e65c35459d52f0d0b890aa5df0cad07a051 upstream.

With Xen changeset 23428 "libxl: Add 'e820_host' option to config file"
the E820 as seen from the host can now be passed into the guest.
This means that a PV guest can now:
 - Use the correct PCI I/O gap. Before these patches, Linux guest would
   boot up and would tell:
   [    0.000000] Allocating PCI resources starting at 40000000 (gap: 40000000:c0000000)
   while in actuality the PCI I/O gap should have been:
   [    0.000000] Allocating PCI resources starting at b0000000 (gap: b0000000:4c000000)

 - The PV domain with PCI devices was limited to 3GB. It now can be booted
   with 4GB, 8GB, or whatever number you want. The PCI devices will now _not_ conflict
   with System RAM. Meaning the drivers can load.

CC: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
CC: linux-pci@vger.kernel.org
[v2: Made the string less broken up. Suggested by Joe Perches]
Signed-off-by: Konrad Rzeszutek Wilk &lt;konrad.wilk@oracle.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PCI quirk: mmc: Always check for lower base frequency quirk for Ricoh 1180:e823</title>
<updated>2011-11-11T17:42:29Z</updated>
<author>
<name>Josh Boyer</name>
<email>jwboyer@redhat.com</email>
</author>
<published>2011-10-05T15:44:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d0dab5614492504dffb2b99c6ba88e77393a3d06'/>
<id>urn:sha1:d0dab5614492504dffb2b99c6ba88e77393a3d06</id>
<content type='text'>
commit 3e309cdf07c930f29a4e0f233e47d399bea34c68 upstream.

Commit 15bed0f2f added a quirk for the e823 Ricoh card reader to lower the
base frequency.  However, the quirk first checks to see if the proprietary
MMC controller is disabled, and returns if so.  On some devices, such as the
Lenovo X220, the MMC controller is already disabled by firmware it seems,
but the frequency change is still needed so sdhci-pci can talk to the cards.
Since the MMC controller is disabled, the frequency fixup was never being run
on these machines.

This moves the e823 check above the MMC controller check so that it always
gets run.

This fixes https://bugzilla.redhat.com/show_bug.cgi?id=722509

Signed-off-by: Josh Boyer &lt;jwboyer@redhat.com&gt;
Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PCI: Disable MPS configuration by default</title>
<updated>2011-10-04T16:52:28Z</updated>
<author>
<name>Jon Mason</name>
<email>mason@myri.com</email>
</author>
<published>2011-10-03T14:50:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5f39e6705faade2e89d119958a8c51b9b6e2c53c'/>
<id>urn:sha1:5f39e6705faade2e89d119958a8c51b9b6e2c53c</id>
<content type='text'>
Add the ability to disable PCI-E MPS turning and using the BIOS
configured MPS defaults.  Due to the number of issues recently
discovered on some x86 chipsets, make this the default behavior.

Also, add the option for peer to peer DMA MPS configuration.  Peer to
peer DMA is outside the scope of this patch, but MPS configuration could
prevent it from working by having the MPS on one root port different
than the MPS on another.  To work around this, simply make the system
wide MPS the smallest possible value (128B).

Signed-off-by: Jon Mason &lt;mason@myri.com&gt;
Acked-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>pci: Don't crash when reading mpss from root complex</title>
<updated>2011-09-13T23:08:31Z</updated>
<author>
<name>Benjamin Herrenschmidt</name>
<email>benh@kernel.crashing.org</email>
</author>
<published>2011-09-13T18:16:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1a4b1a41b8a3d5256019854e851beed063b34344'/>
<id>urn:sha1:1a4b1a41b8a3d5256019854e851beed063b34344</id>
<content type='text'>
In pcie_find_smpss(), we have the following statement:

 	if (dev-&gt;is_hotplug_bridge &amp;&amp; (!list_is_singular(&amp;dev-&gt;bus-&gt;devices) ||
	    dev-&gt;bus-&gt;self-&gt;pcie_type != PCI_EXP_TYPE_ROOT_PORT))

The problem is that at least on my machine, this gets called for the
root complex (virtual P2P bridge), and dev-&gt;bus-&gt;self is NULL since
the parent bus for this is not itself anchor to a PCI device.

This adds the necessary NULL check.

Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Acked-by: Jon Mason &lt;mason@myri.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>PCI: Remove MRRS modification from MPS setting code</title>
<updated>2011-09-10T02:49:58Z</updated>
<author>
<name>Jon Mason</name>
<email>mason@myri.com</email>
</author>
<published>2011-09-08T21:41:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ed2888e906b56769b4ffabb9c577190438aa68b8'/>
<id>urn:sha1:ed2888e906b56769b4ffabb9c577190438aa68b8</id>
<content type='text'>
Modifying the Maximum Read Request Size to 0 (value of 128Bytes) has
massive negative ramifications on some devices.  Without knowing which
devices have this issue, do not modify from the default value when
walking the PCI-E bus in pcie_bus_safe mode.  Also, make pcie_bus_safe
the default procedure.

Tested-by: Sven Schnelle &lt;svens@stackframe.org&gt;
Tested-by: Simon Kirby &lt;sim@hostway.ca&gt;
Tested-by: Stephen M. Cameron &lt;scameron@beardog.cce.hp.com&gt;
Reported-and-tested-by: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Reported-and-tested-by: Niels Ole Salscheider &lt;niels_ole@salscheider-online.de&gt;
References: https://bugzilla.kernel.org/show_bug.cgi?id=42162
Signed-off-by: Jon Mason &lt;mason@myri.com&gt;
Acked-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Fix pointer dereference before call to pcie_bus_configure_settings</title>
<updated>2011-09-10T02:49:58Z</updated>
<author>
<name>Shyam Iyer</name>
<email>shyam.iyer.t@gmail.com</email>
</author>
<published>2011-09-08T21:41:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5307f6d5fb12fd01f9f321bc4a8fd77e74858647'/>
<id>urn:sha1:5307f6d5fb12fd01f9f321bc4a8fd77e74858647</id>
<content type='text'>
Commit b03e7495a862 ("PCI: Set PCI-E Max Payload Size on fabric")
introduced a potential NULL pointer dereference in calls to
pcie_bus_configure_settings due to attempts to access pci_bus self
variables when the self pointer is NULL.

To correct this, verify that the self pointer in pci_bus is non-NULL
before dereferencing it.

Reported-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: Shyam Iyer &lt;shyam_iyer@dell.com&gt;
Signed-off-by: Jon Mason &lt;mason@myri.com&gt;
Acked-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>pci: fix new kernel-doc warning in pci.c</title>
<updated>2011-08-21T01:02:32Z</updated>
<author>
<name>Randy Dunlap</name>
<email>rdunlap@xenotime.net</email>
</author>
<published>2011-08-20T18:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=47c08f3107270e5a439bc0106a308f7c48c9621d'/>
<id>urn:sha1:47c08f3107270e5a439bc0106a308f7c48c9621d</id>
<content type='text'>
Fix new kernel-doc warning in pci.c:

  Warning(drivers/pci/pci.c:3259): No description found for parameter 'mps'
  Warning(drivers/pci/pci.c:3259): Excess function parameter 'rq' description in 'pcie_set_mps'

Signed-off-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Cc: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6</title>
<updated>2011-08-19T17:02:37Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2011-08-19T17:02:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0c3bef612881ee6216a36952ffaabfc35b83545c'/>
<id>urn:sha1:0c3bef612881ee6216a36952ffaabfc35b83545c</id>
<content type='text'>
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6:
  PCI: OF: Don't crash when bridge parent is NULL.
  PCI: export pcie_bus_configure_settings symbol
  PCI: code and comments cleanup
  PCI: make cardbus-bridge resources optional
  PCI: make SRIOV resources optional
  PCI : ability to relocate assigned pci-resources
  PCI: honor child buses add_size in hot plug configuration
  PCI: Set PCI-E Max Payload Size on fabric
</content>
</entry>
<entry>
<title>PCI: OF: Don't crash when bridge parent is NULL.</title>
<updated>2011-08-19T15:51:37Z</updated>
<author>
<name>David Daney</name>
<email>david.daney@cavium.com</email>
</author>
<published>2011-08-16T18:24:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=69566dd8be42dea7a22f625abc96e65bb4b45d1f'/>
<id>urn:sha1:69566dd8be42dea7a22f625abc96e65bb4b45d1f</id>
<content type='text'>
In pcibios_get_phb_of_node(), we will crash while booting if
bus-&gt;bridge-&gt;parent is NULL.

Check for this case and avoid dereferencing the NULL pointer.

Signed-off-by: David Daney &lt;david.daney@cavium.com&gt;
Acked-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Acked-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
</content>
</entry>
</feed>
