04 Jan, 2013
1 commit
-
CONFIG_HOTPLUG is going away as an option. As a result, the __dev*
markings need to be removed.This change removes the use of __devinit, __devexit_p, __devinitconst,
and __devexit from these drivers.Based on patches originally written by Bill Pemberton, but redone by me
in order to handle some of the coding style issues better, by hand.Cc: Bill Pemberton
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Peter Zijlstra
Cc: Daniel Drake
Signed-off-by: Greg Kroah-Hartman
23 Jun, 2012
4 commits
-
Script checkpatch.pl recommends to replace printk(KERN_LVL) with pr_lvl(),
so do it.Reviewed-by: Yinghai Lu
Signed-off-by: Jiang Liu
Signed-off-by: Bjorn Helgaas -
This patch enhances x86 arch-specific code to update MMCONFIG information
when PCI host bridge hotplug event happens.Reviewed-by: Yinghai Lu
Signed-off-by: Jiang Liu
Signed-off-by: Bjorn Helgaas -
Introduce pci_mmcfg_arch_map()/pci_mmcfg_arch_unmap(), which will be used
when supporting PCI root bridge hotplug.Reviewed-by: Yinghai Lu
Signed-off-by: Jiang Liu
Signed-off-by: Bjorn Helgaas -
Use RCU list to protect mmconfig list from dynamic change
when supporting PCI host bridge hotplug.Reviewed-by: Yinghai Lu
Signed-off-by: Jiang Liu
Signed-off-by: Bjorn Helgaas
15 Oct, 2011
1 commit
-
As with any other such change, the goal is to prevent inadvertent
writes to these structures (assuming DEBUG_RODATA is enabled), and to
separate data (possibly frequently) written to from such never getting
modified.Reviewed-by: Ingo Molnar
Signed-off-by: Jan Beulich
Signed-off-by: Jesse Barnes
25 Nov, 2009
7 commits
-
This patch factors out the search for an MMCONFIG region, which was
previously implemented in both mmconfig_32 and mmconfig_64. No functional
change.Reviewed-by: Yinghai Lu
Signed-off-by: Bjorn Helgaas
Signed-off-by: Jesse Barnes -
No functional change; just tidy up printks and make them more consistent
with the rest of PCI.Reviewed-by: Yinghai Lu
Signed-off-by: Bjorn Helgaas
Signed-off-by: Jesse Barnes -
This changes pci_mmcfg_region from a table to a list, to make it easier
to add and remove MMCONFIG regions for PCI host bridge hotplug.Reviewed-by: Yinghai Lu
Signed-off-by: Bjorn Helgaas
Signed-off-by: Jesse Barnes -
The virtual address is only used for x86_64, but it's so much simpler
to manage it as part of the pci_mmcfg_region that I think it's worth
wasting a pointer per MMCONFIG region on x86_32.Reviewed-by: Yinghai Lu
Signed-off-by: Bjorn Helgaas
Signed-off-by: Jesse Barnes -
This only renames the struct pci_mmcfg_region members; no functional change.
Reviewed-by: Yinghai Lu
Signed-off-by: Bjorn Helgaas
Signed-off-by: Jesse Barnes -
This adds a struct pci_mmcfg_region with a little more information
than the struct acpi_mcfg_allocation used previously. The acpi_mcfg
structure is defined by the spec, so we can't change it.To begin with, struct pci_mmcfg_region is basically the same as the
ACPI MCFG version, but future patches will add more information.Reviewed-by: Yinghai Lu
Signed-off-by: Bjorn Helgaas
Signed-off-by: Jesse Barnes -
This factors out the common "bus << 20" expression used when computing the
MMCONFIG address.Reviewed-by: Yinghai Lu
Signed-off-by: Bjorn Helgaas
Signed-off-by: Jesse Barnes
21 Mar, 2009
1 commit
-
Fix mmconfig detection to not assume a single mmconfig space in the
northbridge, paving the way for AMD fam10h + mcp55 CPUs. On those, the
MSR has some range, but the mcp55 pci config will have another one.Also helps the mcp55 + io55 case, where every one will have one range.
If it is mcp55, exclude the range that is used by CPU MSR, in other
words , if the CPU claims busses 0-255, the range in mcp55 is dropped,
because CPU HW will not route those ranges to mcp55 mmconfig to handle
it.Signed-off-by: Yinghai Lu
Signed-off-by: Jesse Barnes
30 Dec, 2008
1 commit
-
Impact: cleanup
Now that arch/x86/pci/pci.h is used in a number of other places as well,
move the lowlevel x86 pci definitions into the architecture include files.
(not to be confused with the existing arch/x86/include/asm/pci.h file,
which provides public details about x86 PCI)Tested on: X86_32_UP, X86_32_SMP and X86_64_SMP
Signed-off-by: Jaswinder Singh Rajput
Acked-by: Jesse Barnes
Signed-off-by: Ingo Molnar
27 Apr, 2008
1 commit
-
For x86_64, need to free pci_mmcfg_virt, and iounmap some pointers
when MMCONF is not reserved in E820 or acpi _CRS and get rejected.Signed-off-by: Yinghai Lu
Cc: Andrew Morton
Cc: Greg KH
Cc: Greg KH
Cc: Andi Kleen
Signed-off-by: Andrew Morton
Signed-off-by: Ingo Molnar
Signed-off-by: Thomas Gleixner
11 Feb, 2008
2 commits
-
We want to allow different implementations of pci_raw_ops for standard
and extended config space on x86. Rather than clutter generic code with
knowledge of this, we make pci_raw_ops private to x86 and use it to
implement the new raw interface -- raw_pci_read() and raw_pci_write().Signed-off-by: Matthew Wilcox
Signed-off-by: Linus Torvalds -
Thanks to Loic Prylli , who originally proposed
this idea.Always using legacy configuration mechanism for the legacy config space
and extended mechanism (mmconf) for the extended config space is
a simple and very logical approach. It's supposed to resolve all
known mmconf problems. It still allows per-device quirks (tweaking
dev->cfg_size). It also allows to get rid of mmconf fallback code.Signed-off-by: Ivan Kokshaysky
Signed-off-by: Matthew Wilcox
Signed-off-by: Linus Torvalds
11 Oct, 2007
1 commit
-
Signed-off-by: Thomas Gleixner
Signed-off-by: Ingo Molnar
