1. 22 9月, 2011 1 次提交
    • O
      hwspinlock/core/omap: fix id issues on multiple hwspinlock devices · c3c1250e
      Ohad Ben-Cohen 提交于
      hwspinlock devices provide system-wide hardware locks that are used
      by remote processors that have no other way to achieve synchronization.
      
      To achieve that, each physical lock must have a system-wide id number
      that is agreed upon, otherwise remote processors can't possibly assume
      they're using the same hardware lock.
      
      Usually boards have a single hwspinlock device, which provides several
      hwspinlocks, and in this case, they can be trivially numbered 0 to
      (num-of-locks - 1).
      
      In case boards have several hwspinlocks devices, a different base id
      should be used for each hwspinlock device (they can't all use 0 as
      a starting id!).
      
      While this is certainly not common, it's just plain wrong to just
      silently use 0 as a base id whenever the hwspinlock driver is probed.
      
      This patch provides a hwspinlock_pdata structure, that boards can use
      to set a different base id for each of the hwspinlock devices they may
      have, and demonstrates how to use it with the omap hwspinlock driver.
      
      While we're at it, make sure the hwspinlock core prints an explicit
      error message in case an hwspinlock is registered with an id number
      that already exists; this will help users catch such base id issues.
      Reported-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      c3c1250e
  2. 11 9月, 2011 3 次提交
  3. 10 9月, 2011 3 次提交
  4. 07 9月, 2011 6 次提交
  5. 05 9月, 2011 2 次提交
    • J
      openrisc: don't use pt_regs in struct sigcontext · d7cb6667
      Jonas Bonn 提交于
      As it was decided not to export struct pt_regs to userspace, struct
      sigcontext shouldn't be using it either.  The pt_regs struct for OpenRISC
      is kernel internal and the layout of the registers may change in the
      future.  The struct user_regs_struct is what is guaranteed to remain
      stable, so struct sigcontext may use that instead.
      
      This patch removes the usage of struct pt_regs in struct sigcontext and
      makes according changes in signal.c to get the register layout right.
      
      The usp field is removed from the sigcontext structure as this information
      is already contained in the user_regs_struct.
      Signed-off-by: NJonas Bonn <jonas@southpole.se>
      Reviewed-by: NEmilio Cota <cota@braap.org>
      d7cb6667
    • P
      OMAP2430: hwmod: musb: add missing terminator to omap2430_usbhsotg_addrs[] · 10167873
      Paul Walmsley 提交于
      Add a missing array terminator to omap2430_usbhsotg_addrs[].  Without
      this terminator, the omap_hwmod resource building code runs off the
      end of the array, resulting in at least this error -- if not worse
      behavior:
      
      [    0.578002] musb-omap2430: failed to claim resource 4
      [    0.583465] omap_device: musb-omap2430: build failed (-16)
      [    0.589294] Could not build omap_device for musb-omap2430 usb_otg_hs
      
      This should have been part of commit
      78183f3f ("omap_hwmod: use a null
      structure record to terminate omap_hwmod_addr_space arrays") but was
      evidently missed.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      10167873
  6. 04 9月, 2011 1 次提交
  7. 02 9月, 2011 2 次提交
  8. 01 9月, 2011 1 次提交
    • D
      xen: use maximum reservation to limit amount of usable RAM · d312ae87
      David Vrabel 提交于
      Use the domain's maximum reservation to limit the amount of extra RAM
      for the memory balloon. This reduces the size of the pages tables and
      the amount of reserved low memory (which defaults to about 1/32 of the
      total RAM).
      
      On a system with 8 GiB of RAM with the domain limited to 1 GiB the
      kernel reports:
      
      Before:
      
      Memory: 627792k/4472000k available
      
      After:
      
      Memory: 549740k/11132224k available
      
      A increase of about 76 MiB (~1.5% of the unused 7 GiB).  The reserved
      low memory is also reduced from 253 MiB to 32 MiB.  The total
      additional usable RAM is 329 MiB.
      
      For dom0, this requires at patch to Xen ('x86: use 'dom0_mem' to limit
      the number of pages for dom0') (c/s 23790)
      
      CC: stable@kernel.org
      Signed-off-by: NDavid Vrabel <david.vrabel@citrix.com>
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      d312ae87
  9. 31 8月, 2011 4 次提交
  10. 30 8月, 2011 5 次提交
  11. 29 8月, 2011 8 次提交
  12. 28 8月, 2011 4 次提交