1. 02 Nov, 2008 1 commit
  2. 31 Oct, 2008 30 commits
  3. 30 Oct, 2008 9 commits
    • Ingo Molnar's avatar
      x86: cpu_index build fix · 1c4acdb4
      Ingo Molnar authored
      fix:
      
       arch/x86/kernel/cpu/common.c: In function 'early_identify_cpu':
       arch/x86/kernel/cpu/common.c:553: error: 'struct cpuinfo_x86' has no member named 'cpu_index'
      
      as cpu_index is only available on SMP.
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      1c4acdb4
    • James Bottomley's avatar
      x86/voyager: fix missing cpu_index initialisation · bfcb4c1b
      James Bottomley authored
      Impact: fix /proc/cpuinfo output on x86/Voyager
      
      Ever since
      
      | commit 92cb7612
      | Author: Mike Travis <travis@sgi.com>
      | Date:   Fri Oct 19 20:35:04 2007 +0200
      |
      |     x86: convert cpuinfo_x86 array to a per_cpu array
      
      We've had an extra field in cpuinfo_x86 which is cpu_index.
      Unfortunately, voyager has never initialised this, although the only
      noticeable impact seems to be that /proc/cpuinfo shows all zeros for
      the processor ids.
      
      Anyway, fix this by initialising the boot CPU properly and setting the
      index when the secondaries update.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      bfcb4c1b
    • James Bottomley's avatar
      x86/voyager: fix compile breakage caused by dc1e35c6 · b3572e36
      James Bottomley authored
      Impact: build fix on x86/Voyager
      
      Given commits like this:
      
      | Author: Suresh Siddha <suresh.b.siddha@intel.com>
      | Date:   Tue Jul 29 10:29:19 2008 -0700
      |
      |     x86, xsave: enable xsave/xrstor on cpus with xsave support
      
      Which deliberately expose boot cpu dependence to pieces of the system,
      I think it's time to explicitly have a variable for it to prevent this
      continual misassumption that the boot CPU is zero.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      b3572e36
    • Linus Torvalds's avatar
      Merge master.kernel.org:/home/rmk/linux-2.6-arm · 7105212b
      Linus Torvalds authored
      * master.kernel.org:/home/rmk/linux-2.6-arm:
        [ARM] 5326/1: AFEB9260: Fix for i2c_board_info structure
        [ARM] mx31ads: Add missing include
        [ARM] MXC: Fix mxc_gpio_get(), which must read PSR register instead DR.
        [ARM] MX3: Use ioremap wrapper to map SoC devices nonshared
        [ARM] gpio_free might sleep, arm architecture
        [ARM] ep93xx: fix OHCI DMA mask
        leds: da903x: (da9030 only) led brightness reversed.
        [ARM] sharpsl_pm: fix compilation w/o CONFIG_PM
        [ARM] pcm037: map AIPS1 and AIPS2 as nonshared area
        [ARM] build fixes for netX serial driver
        [ARM] 5323/1: Remove outdated empeg documentation.
        [ARM] 5299/1: Add maintainer for Mobilepro 900/c
        [ARM] corgi_lcd: fix simultaneous compilation with corgi_bl
        [ARM] pxa/spitz: fix spi cs on spitz
        [ARM] 5322/1: Fix fastpath issue in mmci.c
        [ARM] xsc3: revert writethrough memory-type encoding change
      7105212b
    • Steven Rostedt's avatar
      ftrace: handle archs that do not support irqs_disabled_flags · 9244489a
      Steven Rostedt authored
      Impact: build fix on non-lockdep architectures
      
      Some architectures do not support a way to read the irq flags that
      is set from "local_irq_save(flags)" to determine if interrupts were
      disabled or enabled. Ftrace uses this information to display to the user
      if the trace occurred with interrupts enabled or disabled.
      
      Besides the fact that those archs that do not support this will fail to
      compile, unless they fix it, we do not want to have the trace simply
      say interrupts were not disabled or they were enabled, without knowing
      the real answer.
      
      This patch adds a 'X' in the output to let the user know that the
      architecture they are running on does not support a way for the tracer
      to determine if interrupts were enabled or disabled. It also lets those
      same archs compile with tracing enabled.
      Signed-off-by: default avatarSteven Rostedt <srostedt@redhat.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      9244489a
    • Ravikiran G Thirumalai's avatar
      x86: fix /dev/mem mmap breakage when PAT is disabled · 9e41bff2
      Ravikiran G Thirumalai authored
      Impact: allow /dev/mem mmaps on non-PAT CPUs/platforms
      
      Fix mmap to /dev/mem when CONFIG_X86_PAT is off and CONFIG_STRICT_DEVMEM is
      off
      
      mmap to /dev/mem on kernel memory has been failing since the
      introduction of PAT (CONFIG_STRICT_DEVMEM=n case).   Seems like
      the check to avoid cache aliasing with PAT is kicking in even
      when PAT is disabled. The bug seems to have crept in 2.6.26.
      
      This patch makes sure that the mmap to regular
      kernel memory succeeds if CONFIG_STRICT_DEVMEM=n and
      PAT is disabled, and the checks to avoid cache aliasing
      still happens if PAT is enabled.
      Signed-off-by: default avatarRavikiran Thirumalai <kiran@scalex86.org>
      Tested-by: default avatarTim Sirianni <tim@scalemp.com>
      Cc: <stable@kernel.org>
      Acked-by: default avatarH. Peter Anvin <hpa@zytor.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      9e41bff2
    • James Bottomley's avatar
      x86/voyager: fix compile breakage casued by x86: move prefill_possible_map calling early · ee477524
      James Bottomley authored
      Impact: fix build failure on x86/Voyager
      
      Before:
      
      | commit 329513a3
      | Author: Yinghai Lu <yhlu.kernel@gmail.com>
      | Date:   Wed Jul 2 18:54:40 2008 -0700
      |
      |     x86: move prefill_possible_map calling early
      
      prefill_possible_mask() was hidden under CONFIG_HOTPLUG_CPU rendering
      it invisitble to voyager.  Since this commit it's exposed, but not
      provided by the voyager subarch, so add a dummy stub to fix the link
      breakage.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: Yinghai Lu <yhlu.kernel@gmail.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      ee477524
    • James Bottomley's avatar
      x86: use CONFIG_X86_SMP instead of CONFIG_SMP · 017d9d20
      James Bottomley authored
      Impact: fix x86/Voyager boot
      
      CONFIG_SMP is used for features which work on *all* x86 boxes.
      CONFIG_X86_SMP is used for standard PC like x86 boxes (for things like
      multi core and apics)
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      017d9d20
    • James Bottomley's avatar
      x86/voyager: fix boot breakage caused by x86: boot secondary cpus through initial_code · 08c33308
      James Bottomley authored
      Impact: boot up secondary CPUs as well on x86/Voyager systems
      
      This commit:
      
      | commit 3e970473
      | Author: Glauber Costa <gcosta@redhat.com>
      | Date:   Wed May 28 13:01:54 2008 -0300
      |
      |     x86: boot secondary cpus through initial_code
      
      removed the use of initialize_secondary.  However, it didn't update
      voyager, so the secondary cpus no longer boot.  Fix this by adding the
      initial_code switch to voyager as well.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: Glauber Costa <gcosta@redhat.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      08c33308