1. 10 1月, 2009 3 次提交
  2. 09 1月, 2009 29 次提交
  3. 08 1月, 2009 8 次提交
    • B
      [ARM] footbridge: dc21285.c warning fixes · 0dc6c490
      Ben Dooks 提交于
      The dc21285 requests a number of IRQs that it doesn't really
      care whether they get added. Change to use a macro that ensures
      that at-least the user gets warned if they fail to add, which
      also stops the warnings from __unused_result on request_irq().
      
      dc21285.c:337: warning: ignoring return value of 'request_irq', declared with attribute warn_unused_result
      dc21285.c:339: warning: ignoring return value of 'request_irq', declared with attribute warn_unused_result
      dc21285.c:341: warning: ignoring return value of 'request_irq', declared with attribute warn_unused_result
      dc21285.c:343: warning: ignoring return value of 'request_irq', declared with attribute warn_unused_result
      dc21285.c:345: warning: ignoring return value of 'request_irq', declared with attribute warn_unused_result
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      0dc6c490
    • B
      [ARM] footbridge: add isa_init_irq() to common header · 39ebfd3f
      Ben Dooks 提交于
      isa_init_irq() is defined in arch/arm/mach-footbridge/isa-irq.c
      and used in arch/arm/mach-footbridge/common.c but there is no
      definition in any header. Move the definition in common.c to
      common.h to stop the sparse warning:
      
      isa-irq.c:118:13: warning: symbol 'isa_init_irq' was not declared.
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      39ebfd3f
    • B
      [ARM] arch/arm/kernel/isa.c: missing definition of register_isa_ports · 87e0d6cc
      Ben Dooks 提交于
      arch/arm/kernel/isa.c should include <linux/io.h> to get the
      definition of register_io_ports() at-least when compiling for
      footbridge to fix the following sparse warning:
      
      isa.c:68:1: warning: symbol 'register_isa_ports' was not declared.
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      87e0d6cc
    • R
      25006644
    • C
      powerpc/oprofile: IBM CELL: add SPU event profiling support · 88382329
      Carl Love 提交于
      This patch adds the SPU event based profiling funcitonality for the
      IBM Cell processor.  Previously, the CELL OProfile kernel code supported
      PPU event, PPU cycle profiling and SPU cycle profiling.   The addition of
      SPU event profiling allows the users to identify where in their SPU code
      various SPU evnets are occuring.  This should help users further identify
      issues with their code.  Note, SPU profiling has some limitations due to HW
      constraints.  Only one event at a time can be used for profiling and SPU event
      profiling must be time sliced across all of the SPUs in a node.
      
      The patch adds a new arch specific file to the OProfile file system. The
      file has bit 0 set to indicate that the kernel supports SPU event profiling.
      The user tool must check this file/bit to make sure the kernel supports
      SPU event profiling before trying to do SPU event profiling.  The user tool
      check is part of the user tool patch for SPU event profiling.
      Signed-off-by: NCarl Love <carll@us.ibm.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      88382329
    • R
      powerpc/oprofile: fix cell/pr_util.h · 014cef91
      Robert Richter 提交于
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      014cef91
    • C
      powerpc/oprofile: IBM CELL: cleanup and restructuring · 9b93418e
      Carl Love 提交于
      This patch restructures and cleans up the code a bit to make it
      easier to add new functionality later.  The patch makes no
      functional changes to the existing code.
      Signed-off-by: NCarl Love <carll@us.ibm.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      9b93418e
    • D
      NOMMU: Make VMAs per MM as for MMU-mode linux · 8feae131
      David Howells 提交于
      Make VMAs per mm_struct as for MMU-mode linux.  This solves two problems:
      
       (1) In SYSV SHM where nattch for a segment does not reflect the number of
           shmat's (and forks) done.
      
       (2) In mmap() where the VMA's vm_mm is set to point to the parent mm by an
           exec'ing process when VM_EXECUTABLE is specified, regardless of the fact
           that a VMA might be shared and already have its vm_mm assigned to another
           process or a dead process.
      
      A new struct (vm_region) is introduced to track a mapped region and to remember
      the circumstances under which it may be shared and the vm_list_struct structure
      is discarded as it's no longer required.
      
      This patch makes the following additional changes:
      
       (1) Regions are now allocated with alloc_pages() rather than kmalloc() and
           with no recourse to __GFP_COMP, so the pages are not composite.  Instead,
           each page has a reference on it held by the region.  Anything else that is
           interested in such a page will have to get a reference on it to retain it.
           When the pages are released due to unmapping, each page is passed to
           put_page() and will be freed when the page usage count reaches zero.
      
       (2) Excess pages are trimmed after an allocation as the allocation must be
           made as a power-of-2 quantity of pages.
      
       (3) VMAs are added to the parent MM's R/B tree and mmap lists.  As an MM may
           end up with overlapping VMAs within the tree, the VMA struct address is
           appended to the sort key.
      
       (4) Non-anonymous VMAs are now added to the backing inode's prio list.
      
       (5) Holes may be punched in anonymous VMAs with munmap(), releasing parts of
           the backing region.  The VMA and region structs will be split if
           necessary.
      
       (6) sys_shmdt() only releases one attachment to a SYSV IPC shared memory
           segment instead of all the attachments at that addresss.  Multiple
           shmat()'s return the same address under NOMMU-mode instead of different
           virtual addresses as under MMU-mode.
      
       (7) Core dumping for ELF-FDPIC requires fewer exceptions for NOMMU-mode.
      
       (8) /proc/maps is now the global list of mapped regions, and may list bits
           that aren't actually mapped anywhere.
      
       (9) /proc/meminfo gains a line (tagged "MmapCopy") that indicates the amount
           of RAM currently allocated by mmap to hold mappable regions that can't be
           mapped directly.  These are copies of the backing device or file if not
           anonymous.
      
      These changes make NOMMU mode more similar to MMU mode.  The downside is that
      NOMMU mode requires some extra memory to track things over NOMMU without this
      patch (VMAs are no longer shared, and there are now region structs).
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Tested-by: NMike Frysinger <vapier.adi@gmail.com>
      Acked-by: NPaul Mundt <lethal@linux-sh.org>
      8feae131