1. 08 9月, 2014 1 次提交
    • A
      PPC: mac99: Move NVRAM to page boundary when necessary · 261265cc
      Alexander Graf 提交于
      When running KVM we have to adhere to host page boundaries for memory slots.
      Unfortunately the NVRAM on mac99 is a 4k RAM hole inside of an MMIO flash
      area.
      
      So if our host is configured with 64k page size, we can't use the mac99 target
      with KVM. This is a real shame, as this limitation is not really an issue - we
      can easily map NVRAM somewhere else and at least Linux and Mac OS X use it
      at their new location.
      
      So in that emergency case when it's about failing to run at all and moving NVRAM
      to a place it shouldn't be at, choose the latter.
      
      This patch enables -M mac99 with KVM on 64k page size hosts.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      261265cc
  2. 16 6月, 2014 1 次提交
  3. 08 4月, 2014 1 次提交
    • A
      PPC: Clean up DECR implementation · e81a982a
      Alexander Graf 提交于
      There are 3 different variants of the decrementor for BookE and BookS.
      
      The BookE variant sets TSR[DIS] to 1 when the DEC value becomes 1 or 0. TSR[DIS]
      is then the indicator whether the decrementor interrupt line is asserted or not.
      
      The old BookS variant treats DEC as an edge interrupt that gets triggered when
      the DEC value's top bit turns 1 from 0.
      
      The new BookS variant maintains the assertion bit inside DEC itself. Whenever
      the DEC value becomes negative (top bit set) the DEC interrupt line is asserted.
      
      So far we implemented mostly the old BookS variant. Let's do them all properly.
      
      This fixes booting pseries ppc64 guest images in TCG mode for me.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      e81a982a
  4. 03 12月, 2013 1 次提交
  5. 10 7月, 2013 1 次提交
  6. 01 7月, 2013 1 次提交
  7. 09 4月, 2013 1 次提交
    • P
      hw: move headers to include/ · 0d09e41a
      Paolo Bonzini 提交于
      Many of these should be cleaned up with proper qdev-/QOM-ification.
      Right now there are many catch-all headers in include/hw/ARCH depending
      on cpu.h, and this makes it necessary to compile these files per-target.
      However, fixing this does not belong in these patches.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      0d09e41a
  8. 16 2月, 2013 1 次提交
  9. 19 1月, 2013 1 次提交
  10. 19 12月, 2012 3 次提交
  11. 15 3月, 2012 1 次提交
  12. 06 10月, 2011 1 次提交
  13. 02 4月, 2011 1 次提交
  14. 25 9月, 2010 1 次提交
  15. 27 8月, 2010 1 次提交
    • A
      PPC: Add PV hypercall transport through fw_cfg · 45024f09
      Alexander Graf 提交于
      On KVM for PPC we need to tell the guest which instructions to use when
      doing a hypercall. The clean way to do this is to go through an ioctl
      from userspace and passing it on to the guest using the device tree.
      
      So let's do the qemu part here: read out the hypercall and pass it on
      to the guest's fw_cfg so openBIOS can read it out and expose it again.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      45024f09
  16. 14 2月, 2010 2 次提交
    • A
      PPC: tell the guest about the time base frequency · dc333cd6
      Alexander Graf 提交于
      Our guest systems need to know by how much the timebase increases every second,
      so there usually is a "timebase-frequency" property in the cpu leaf of the
      device tree.
      
      This property is missing in OpenBIOS.
      
      With qemu, Linux's fallback timebase speed and qemu's internal timebase speed
      match up. With KVM, that is no longer true. The guest is running at the same
      timebase speed as the host.
      
      This leads to massive timing problems. On my test machine, a "sleep 2" takes
      about 14 seconds with KVM enabled.
      
      This patch exports the timebase frequency to OpenBIOS, so it can then put them
      into the device tree.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      dc333cd6
    • A
      PPC: Use Mac99_U3 type on ppc64 · 0f921197
      Alexander Graf 提交于
      The "Mac99" type so far defines a "U2" based configuration. Unfortunately,
      there have never been any U2 based PPC64 machines. That's what the U3 was
      developed for.
      
      So let's split the Mac99 machine in a PPC64 and a PPC32 machine. The PPC32
      machine stays "Mac99", while the PPC64 one becomes "Mac99_U3". All peripherals
      stay the same.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      0f921197
  17. 21 12月, 2009 1 次提交
  18. 02 10月, 2009 2 次提交
  19. 26 8月, 2009 1 次提交
  20. 15 8月, 2009 1 次提交
  21. 08 8月, 2009 1 次提交
  22. 03 3月, 2009 1 次提交
  23. 09 1月, 2009 1 次提交
  24. 26 10月, 2008 1 次提交
  25. 18 11月, 2007 1 次提交