1. 23 Dec, 2011 1 commit
  2. 11 Dec, 2011 1 commit
  3. 07 Dec, 2011 1 commit
  4. 06 Dec, 2011 4 commits
    • Will Deacon's avatar
      ARM: 7185/1: perf: don't assign platform_device on unsupported CPUs · 6bd05409
      Will Deacon authored
      
      
      In the unlikely case that a platform registers a PMU platform_device
      when running on a CPU that is unsupported by perf, we will encounter a
      NULL dereference when trying to assign the platform_device to the
      cpu_pmu structure.
      
      This patch checks that the CPU is supported by perf before assigning
      the platform_device.
      Reported-by: default avatarPawel Moll <pawel.moll@arm.com>
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      6bd05409
    • Uwe Kleine-König's avatar
      ARM: 7187/1: fix unwinding for XIP kernels · de66a979
      Uwe Kleine-König authored
      
      
      The linker places the unwind tables in readonly sections. So when using
      an XIP kernel these are located in ROM and cannot be modified.
      For that reason the current approach to convert the relative offsets in
      the unwind index to absolute addresses early in the boot process doesn't
      work with XIP.
      
      The offsets in the unwind index section are signed 31 bit numbers and
      the structs are sorted by this offset. So it first has offsets between
      0x40000000 and 0x7fffffff (i.e. the negative offsets) and then offsets
      between 0x00000000 and 0x3fffffff. When seperating these two blocks the
      numbers are sorted even when interpreting the offsets as unsigned longs.
      
      So determine the first non-negative entry once and track that using the
      new origin pointer. The actual bisection can then use a plain unsigned
      long comparison. The only thing that makes the new bisection more
      complicated is that the offsets are relative to their position in the
      index section, so the key to search needs to be adapted accordingly in
      each step.
      
      Moreover several consts are added to catch future writes and rename the
      member "addr" of struct unwind_idx to "addr_offset" to better match the
      new semantic. (This has the additional benefit of breaking eventual
      users at compile time to make them aware of the change.)
      
      In my tests the new algorithm was a tad faster than the original and has
      the additional upside of not needing the initial conversion and so saves
      some boot time and it's possible to unwind even earlier.
      Acked-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
      Acked-by: default avatarNicolas Pitre <nico@fluxnic.net>
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      de66a979
    • Nicolas Pitre's avatar
      ARM: 7186/1: fix Kconfig issue with PHYS_OFFSET and !MMU · 974c0724
      Nicolas Pitre authored
      Commit 1b9f95f8
      
       (ARM: prepare for removal of a bunch of <mach/memory.h>
      files) introduced CONFIG_PHYS_OFFSET but the Kconfig hex prompt did not
      provide a default value.
      
      This has the undesired side effect of breaking a reportedly used
      trick for updating defconfigs on the fly for routine buildtesting
      across all arch and all platforms, i.e.
      
      	cp /path/to/somedefconfig .config ; yes "" | make oldconfig
      
      because the config system will endlessly loop until a valid address is
      provided.
      
      However we can't just pick a random default value since it is likely to
      be wrong for the majority of the boards as the right answer for this
      option is quite varied.  So the fact that the config system insists on
      having a proper value be entered is actually a good thing.
      
      It turns out that only at91x40_defconfig has this problem because it has
      CONFIG_MMU=n. However, in the !MMU case, there is already a CONFIG_DRAM_BASE
      value that can be used here.  So let's use that as a default in that case
      and suppress the redundant CONFIG_PHYS_OFFSET prompt.
      
      Eventually the DRAM_BASE config option could simply be replaced by
      PHYS_OFFSET directly, but that's a larger change better suited for later.
      Reported-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: default avatarNicolas Pitre <nico@linaro.org>
      Acked-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      974c0724
    • Joerg Roedel's avatar
      iommu/msm: Fix compile error in mach-msm/devices-iommu.c · 96f176a3
      Joerg Roedel authored
      
      
      Fix compile error due to missing <linux/module.h> include.
      Signed-off-by: default avatarJoerg Roedel <joerg.roedel@amd.com>
      96f176a3
  5. 05 Dec, 2011 7 commits
  6. 01 Dec, 2011 14 commits
  7. 30 Nov, 2011 5 commits
  8. 29 Nov, 2011 2 commits
  9. 28 Nov, 2011 1 commit
  10. 26 Nov, 2011 4 commits