1. 24 2月, 2012 2 次提交
  2. 01 11月, 2011 1 次提交
  3. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  4. 02 4月, 2009 1 次提交
  5. 05 2月, 2009 1 次提交
  6. 01 12月, 2008 1 次提交
  7. 07 3月, 2008 1 次提交
  8. 10 7月, 2007 1 次提交
  9. 21 3月, 2007 1 次提交
  10. 19 3月, 2007 1 次提交
  11. 03 2月, 2007 1 次提交
    • J
      Altix: ACPI SSDT PCI device support · 6f09a925
      John Keller 提交于
      Add SN platform support for running with an ACPI
      capable PROM that defines PCI devices in SSDT
      tables. There is a SSDT table for every occupied
      slot on a root bus, containing info for every
      PPB and/or device on the bus. The SSDTs will be
      dynamically loaded/unloaded at hotplug enable/disable.
      
      Platform specific information that is currently
      passed via a SAL call, will now be passed via the
      Vendor resource in the ACPI Device object(s) defined
      in each SSDT.
      Signed-off-by: NJohn Keller <jpk@sgi.com>
      Cc: Greg KH <greg@kroah.com>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      6f09a925
  12. 02 12月, 2006 2 次提交
    • J
      Altix: Initial ACPI support - ROM shadowing. · a2302c68
      John Keller 提交于
      Support a shadowed ROM when running with an ACPI capable PROM.
      
      Define a new dev.resource flag IORESOURCE_ROM_BIOS_COPY to
      describe the case of a BIOS shadowed ROM, which can then
      be used to avoid pci_map_rom() making an unneeded call to
      pci_enable_rom().
      Signed-off-by: NJohn Keller <jpk@sgi.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      a2302c68
    • J
      Altix: Add initial ACPI IO support · 8ea6091f
      John Keller 提交于
      First phase in introducing ACPI support to SN.
      In this phase, when running with an ACPI capable PROM,
      the DSDT will define the root busses and all SN nodes
      (SGIHUB, SGITIO). An ACPI bus driver will be registered
      for the node devices, with the acpi_pci_root_driver being
      used for the root busses. An ACPI vendor descriptor is
      now used to pass platform specific information for both
      nodes and busses, eliminating the need for the current
      SAL calls. Also, with ACPI support, SN fixup code is no longer
      needed to initiate the PCI bus scans, as the acpi_pci_root_driver
      does that.
      
      However, to maintain backward compatibility with non-ACPI capable
      PROMs, none of the current 'fixup' code can been deleted, though
      much restructuring has been done. For example, the bulk of the code
      in io_common.c is relocated code that is now common regardless
      of what PROM is running, while io_acpi_init.c and io_init.c contain
      routines specific to an ACPI or non ACPI capable PROM respectively.
      
      A new pci bus fixup platform vector has been created to provide
      a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
      
      The size of io_space[] has been increased to support systems with
      large IO configurations.
      Signed-off-by: NJohn Keller <jpk@sgi.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      8ea6091f
  13. 22 6月, 2006 1 次提交
  14. 25 3月, 2006 1 次提交
  15. 28 2月, 2006 1 次提交
  16. 16 2月, 2006 2 次提交
  17. 10 2月, 2006 2 次提交
  18. 03 2月, 2006 2 次提交
  19. 27 1月, 2006 1 次提交
  20. 18 1月, 2006 1 次提交
  21. 17 1月, 2006 1 次提交
  22. 14 1月, 2006 1 次提交
    • P
      [IA64-SGI] Fix sn_flush_device_kernel & spinlock initialization · 6d6e4200
      Prarit Bhargava 提交于
      This patch separates the sn_flush_device_list struct into kernel and
      common (both kernel and PROM accessible) structures.  As it was, if the
      size of a spinlock_t changed (due to additional CONFIG options, etc.) the
      sal call which populated the sn_flush_device_list structs would erroneously
      write data (and cause memory corruption and/or a panic).
      
      This patch does the following:
      
      1.  Removes sn_flush_device_list and adds sn_flush_device_common and
      sn_flush_device_kernel.
      
      2.  Adds a new SAL call to populate a sn_flush_device_common struct per
      device, not per widget as previously done.
      
      3.  Correctly initializes each device's sn_flush_device_kernel spinlock_t
      struct (before it was only doing each widget's first device).
      Signed-off-by: NPrarit Bhargava <prarit@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      6d6e4200
  23. 07 12月, 2005 1 次提交
    • J
      [IA64-SGI] altix: pci_window fixup · 3ec829b6
      John Keller 提交于
      Altix only patch to add fixup code that sets up
      pci_controller->window. This code is a temporary
      fix until ACPI support on Altix is added.
      
      Also, corrects the usage of pci_dev->sysdata,
      which had previously been used to reference
      platform specific device info, to now point to
      a pci_controller struct.
      Signed-off-by: NJohn Keller <jpk@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      3ec829b6
  24. 11 11月, 2005 1 次提交
  25. 16 9月, 2005 1 次提交
    • J
      [IA64] Cleanup use of various #defines related to nodes · 24ee0a6d
      Jack Steiner 提交于
      Some of the SN code & #defines related to compact nodes & IO discovery
      have gotten stale over the years. This patch attempts to clean them up.
      Some of the various SN MAX_xxx #defines were also unclear & misused.
      
      The primary changes are:
      
      	- use MAX_NUMNODES. This is the generic linux #define for the number
      	  of nodes that are known to the generic kernel. Arrays & loops
      	  for constructs that are 1:1 with linux-defined nodes should
      	  use the linux #define - not an SN equivalent.
      
      	- use MAX_COMPACT_NODES for MAX_NUMNODES + NUM_TIOS. This is the
      	  number of nodes in the SSI system. Compact nodes are a hack to
      	  get around the IA64 architectural limit of 256 nodes. Large SGI
      	  systems have more than 256 nodes. When we upgrade to ACPI3.0,
      	  I _hope_ that all nodes will be real nodes that are known to
      	  the generic kernel. That will allow us to delete the notion
      	  of "compact nodes".
      
      	- add MAX_NUMALINK_NODES for the total number of nodes that
      	  are in the numalink domain - all partitions.
      
      	- simplified (understandable) scan_for_ionodes()
      
      	- small amount of cleanup related to cnodes
      Signed-off-by: NJack Steiner <steiner@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      24ee0a6d
  26. 08 9月, 2005 1 次提交
  27. 17 8月, 2005 2 次提交
  28. 12 8月, 2005 2 次提交
  29. 13 7月, 2005 1 次提交
    • C
      [IA64] Altix pcibus_to_node implementation · 7c2a6c62
      Christoph Lameter 提交于
      The Altix subarch does not provide node information via ACPI. Instead hooks
      are used to fixup pci structures. This patch determines the nodes for Altix
      PCI busses.
      
      Remote Bridges:
      ---------------
      Altix supports remote I/O nodes without memory or processors but with bridges.
      The TIOCA type of bridge is an AGP bridge and the PROM provides information
      about the closest node. That information will be returned by pcibus_to_node.
      
      The TIOCP remote bridge type is a PCI bridge but the PROM does not provide a
      closest node id. pcibus_to_node will return -1 for devices on those bridges
      meaning that device control structures may be allocated on any node.
      
      Safeguard:
      ----------
      Should the fixups result in invalid node information for a pci controller then
      a warning will be printed and pcibus_to_node will return -1.
      
      
      This patch also fixes the "FIXME" in sn_dma_alloc_coherent. This means that
      dma_alloc_coherent will now use alloc_pages_node to allocate memory local to
      the node that the PCI device is connected to.
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      7c2a6c62
  30. 07 7月, 2005 3 次提交
  31. 29 6月, 2005 1 次提交