1. 05 12月, 2017 1 次提交
    • D
      Revert "powerpc: Do not call ppc_md.panic in fadump panic notifier" · ab9dbf77
      David Gibson 提交于
      This reverts commit a3b2cb30.
      
      That commit tried to fix problems with panic on powerpc in certain
      circumstances, where some output from the generic panic code was being
      dropped.
      
      Unfortunately, it breaks things worse in other circumstances. In
      particular when running a PAPR guest, it will now attempt to reboot
      instead of informing the hypervisor (KVM or PowerVM) that the guest
      has crashed. The crash notification is important to some
      virtualization management layers.
      
      Revert it for now until we can come up with a better solution.
      
      Fixes: a3b2cb30 ("powerpc: Do not call ppc_md.panic in fadump panic notifier")
      Cc: stable@vger.kernel.org # v4.14+
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      [mpe: Tweak change log a bit]
      Signed-off-by: NMichael Ellerman <mpe@ellerman.id.au>
      ab9dbf77
  2. 31 8月, 2017 1 次提交
  3. 30 11月, 2016 1 次提交
  4. 21 7月, 2016 2 次提交
  5. 14 7月, 2016 1 次提交
  6. 19 11月, 2014 1 次提交
    • M
      powerpc: Remove more traces of bootmem · e39f223f
      Michael Ellerman 提交于
      Although we are now selecting NO_BOOTMEM, we still have some traces of
      bootmem lying around. That is because even with NO_BOOTMEM there is
      still a shim that converts bootmem calls into memblock calls, but
      ultimately we want to remove all traces of bootmem.
      
      Most of the patch is conversions from alloc_bootmem() to
      memblock_virt_alloc(). In general a call such as:
      
        p = (struct foo *)alloc_bootmem(x);
      
      Becomes:
      
        p = memblock_virt_alloc(x, 0);
      
      We don't need the cast because memblock_virt_alloc() returns a void *.
      The alignment value of zero tells memblock to use the default alignment,
      which is SMP_CACHE_BYTES, the same value alloc_bootmem() uses.
      
      We remove a number of NULL checks on the result of
      memblock_virt_alloc(). That is because memblock_virt_alloc() will panic
      if it can't allocate, in exactly the same way as alloc_bootmem(), so the
      NULL checks are and always have been redundant.
      
      The memory returned by memblock_virt_alloc() is already zeroed, so we
      remove several memsets of the result of memblock_virt_alloc().
      
      Finally we convert a few uses of __alloc_bootmem(x, y, MAX_DMA_ADDRESS)
      to just plain memblock_virt_alloc(). We don't use memblock_alloc_base()
      because MAX_DMA_ADDRESS is ~0ul on powerpc, so limiting the allocation
      to that is pointless, 16XB ought to be enough for anyone.
      Signed-off-by: NMichael Ellerman <mpe@ellerman.id.au>
      e39f223f
  7. 03 11月, 2014 1 次提交
    • A
      powerpc: Convert power off logic to pm_power_off · 9178ba29
      Alexander Graf 提交于
      The generic Linux framework to power off the machine is a function pointer
      called pm_power_off. The trick about this pointer is that device drivers can
      potentially implement it rather than board files.
      
      Today on powerpc we set pm_power_off to invoke our generic full machine power
      off logic which then calls ppc_md.power_off to invoke machine specific power
      off.
      
      However, when we want to add a power off GPIO via the "gpio-poweroff" driver,
      this card house falls apart. That driver only registers itself if pm_power_off
      is NULL to ensure it doesn't override board specific logic. However, since we
      always set pm_power_off to the generic power off logic (which will just not
      power off the machine if no ppc_md.power_off call is implemented), we can't
      implement power off via the generic GPIO power off driver.
      
      To fix this up, let's get rid of the ppc_md.power_off logic and just always use
      pm_power_off as was intended. Then individual drivers such as the GPIO power off
      driver can implement power off logic via that function pointer.
      
      With this patch set applied and a few patches on top of QEMU that implement a
      power off GPIO on the virt e500 machine, I can successfully turn off my virtual
      machine after halt.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      [mpe: Squash into one patch and update changelog based on cover letter]
      Signed-off-by: NMichael Ellerman <mpe@ellerman.id.au>
      9178ba29
  8. 10 9月, 2012 1 次提交
  9. 08 12月, 2011 1 次提交
  10. 01 11月, 2011 1 次提交
  11. 15 6月, 2009 1 次提交
  12. 28 4月, 2009 1 次提交
  13. 02 4月, 2009 1 次提交
  14. 16 1月, 2009 1 次提交
  15. 23 12月, 2008 1 次提交
  16. 19 11月, 2008 1 次提交
  17. 26 8月, 2008 1 次提交
  18. 01 4月, 2008 2 次提交
  19. 09 10月, 2007 2 次提交
  20. 30 8月, 2007 1 次提交
  21. 03 8月, 2007 1 次提交
  22. 28 6月, 2007 6 次提交
  23. 12 5月, 2007 1 次提交
  24. 02 5月, 2007 1 次提交
  25. 16 2月, 2007 1 次提交
  26. 13 2月, 2007 1 次提交
  27. 07 2月, 2007 3 次提交
  28. 04 12月, 2006 2 次提交
    • A
      [POWERPC] ps3: multiplatform build fixes · e22ba7e3
      Arnd Bergmann 提交于
      A few code paths need to check whether or not they are running
      on the PS3's LV1 hypervisor before making hcalls. This introduces
      a new firmware feature bit for this, FW_FEATURE_PS3_LV1.
      
      Now when both PS3 and IBM_CELL_BLADE are enabled, but not PSERIES,
      FW_FEATURE_PS3_LV1 and FW_FEATURE_LPAR get enabled at compile time,
      which is a bug. The same problem can also happen for (PPC_ISERIES &&
      !PPC_PSERIES && PPC_SOMETHING_ELSE). In order to solve this, I
      introduce a new CONFIG_PPC_NATIVE option that is set when at least
      one platform is selected that can run without a hypervisor and then
      turns the firmware feature check into a run-time option.
      
      The new cell oprofile support that was recently merged does not
      work on hypervisor based platforms like the PS3, therefore make
      it depend on PPC_CELL_NATIVE instead of PPC_CELL. This may change
      if we get oprofile support for PS3.
      Signed-off-by: NArnd Bergmann <arnd.bergmann@de.ibm.com>
      e22ba7e3
    • G
      [POWERPC] ps3: add support for ps3 platform · f58a9d17
      Geoff Levand 提交于
      Adds the core platform support for the PS3 game console and other devices
      using the PS3 hypervisor.
      Signed-off-by: NGeoff Levand <geoffrey.levand@am.sony.com>
      Signed-off-by: NArnd Bergmann <arnd.bergmann@de.ibm.com>
      f58a9d17