1. 20 Jun, 2013 18 commits
  2. 09 Jun, 2013 1 commit
  3. 31 May, 2013 1 commit
    • Srivatsa S. Bhat's avatar
      powerpc/pseries: Always enable CONFIG_HOTPLUG_CPU on PSERIES SMP · f274ef87
      Srivatsa S. Bhat authored
      Adam Lackorzynski reported the following build failure on
      !CONFIG_HOTPLUG_CPU configuration:
        CC      arch/powerpc/kernel/rtas.o
      arch/powerpc/kernel/rtas.c: In function ‘rtas_cpu_state_change_mask’:
      arch/powerpc/kernel/rtas.c:843:4: error: implicit declaration of function ‘cpu_down’ [-Werror=implicit-function-declaration]
      cc1: all warnings being treated as errors
      make[1]: *** [arch/powerpc/kernel/rtas.o] Error 1
      make: *** [arch/powerpc/kernel] Error 2
      The build fails because cpu_down() is defined only under CONFIG_HOTPLUG_CPU.
      Looking further, the mobility code in pseries is one of the call-sites which
      uses rtas_ibm_suspend_me(), which in turn calls rtas_cpu_state_change_mask().
      And the mobility code is unconditionally compiled-in (it does not fall under
      any Kconfig option). And commit 120496ac
       (powerpc: Bring all threads online
      prior to migration/hibernation) which introduced this build regression is
      critical for the proper functioning of the migration code. So it appears
      that the only solution to this problem is to enable CONFIG_HOTPLUG_CPU if
      SMP is enabled on PPC_PSERIES platforms. So make that change in the Kconfig.
      Reported-by: default avatarAdam Lackorzynski <adam@os.inf.tu-dresden.de>
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarSrivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
  4. 24 May, 2013 4 commits
  5. 14 May, 2013 6 commits
  6. 10 May, 2013 1 commit
  7. 08 May, 2013 1 commit
    • Benjamin Herrenschmidt's avatar
      powerpc/powernv: Properly drop characters if console is closed · 1de1455f
      Benjamin Herrenschmidt authored
      If the firmware returns an error such as "closed" (or hardware
      error), we should drop characters.
      Currently we only do that when a firmware compatible with OPAL v2
      APIs is detected, in the code that calls opal_console_write_buffer_space(),
      which didn't exist with OPAL v1 (or didn't work).
      However, when enabling early debug consoles, the flag indicating
      that v2 is supported isn't set yet, causing us, in case of errors
      or closed console, to spin forever.
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
  8. 06 May, 2013 3 commits
  9. 05 May, 2013 5 commits