Re: [RFC] [Patch] calgary iommu: Use the first kernel's tce tables in kdump

Hi Muli, I have tried to work with CCR ,CSR, CSMR, CSAR, CFGRW, GBRERRM registers but have been unable to make calgary generate an exception upon error condition. In alloc_tce_table() , I am setting WRITE_ONLY access permission bit to tce entries but it isn't helping. Would you kindly let

Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue

Arjan van de Ven wrote: 3) mmconfig might or might not be enabled, depending on which driver is loaded, whether it called an API or not. Even LESS testing by hw vendors than #2. Maybe even "never" Inconsistent (config access depends on device) the "depends on device" is even

Re: [RFC/PATCH 3/4] pci: Remove pci_enable_device_bars()

On Tue, Dec 18, 2007 at 10:01:14AM +1100, Benjamin Herrenschmidt wrote: > Now that all in-tree users are gone, this removes pci_enable_device_bars() > completely. Almost completely. Patch below removes pci_enable_device_bars() from Documentation/pci.txt . (And I'd be happy to review patches to pc

Re: [RFC/PATCH 2/4] pci: Remove users of pci_enable_device_bars()

Just a style nit... On Tue, Dec 18, 2007 at 10:01:14AM +1100, Benjamin Herrenschmidt wrote: > This patch converts users of pci_enable_device_bars() to the new > pci_enable_device_{io,mem} interface. > > The new API fits nicely, except maybe for the QLA case where a bit of > code re-organization m

Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue

Ivan Kokshaysky wrote: On Sun, Dec 23, 2007 at 12:44:30AM -0500, Jeff Garzik wrote: Failures are more predictable and more consistent with an all-or-none scenario. The all-or-none solutions are the least complex on the software side, and far more widely tested than any mixed config access sche

Re: [RFC/PATCH 4/4] [POWERPC] pci: Disable IO/Mem on a device when resources can't be allocated

On Tue, Dec 18, 2007 at 10:01:15AM +1100, Benjamin Herrenschmidt wrote: > This patch changes the PowerPC PCI code to disable IO and/or Memory > decoding on a PCI device when a resource of that type failed to be > allocated. This is done to avoid having unallocated dangling BARs enabled > that might

Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue

Linus Torvalds wrote: (For example: I have three machines that I know have working MMCONF. On only one of theose does Linux actually even enable MMCONF accesses, because on the two other ones the BIOSes do the crazy "put it in some space that is reserved by PnP crap later", so we actually refus

<    1   2   3