1. 04 12月, 2009 2 次提交
  2. 17 11月, 2009 1 次提交
  3. 13 11月, 2009 1 次提交
  4. 12 10月, 2009 1 次提交
  5. 05 10月, 2009 2 次提交
  6. 02 10月, 2009 2 次提交
  7. 21 9月, 2009 1 次提交
  8. 12 9月, 2009 1 次提交
    • B
      Fix sys-queue.h conflict for good · 72cf2d4f
      Blue Swirl 提交于
      Problem: Our file sys-queue.h is a copy of the BSD file, but there are
      some additions and it's not entirely compatible. Because of that, there have
      been conflicts with system headers on BSD systems. Some hacks have been
      introduced in the commits 15cc9235,
      f40d7537,
      96555a96 and
      3990d09a but the fixes were fragile.
      
      Solution: Avoid the conflict entirely by renaming the functions and the
      file. Revert the previous hacks.
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      72cf2d4f
  9. 28 8月, 2009 1 次提交
  10. 28 7月, 2009 4 次提交
    • A
      Revert "Fake dirty loggin when it's not there" · 6e489f3f
      Anthony Liguori 提交于
      This reverts commit bd836776.
      
      PPC should just implement dirty logging so we can avoid all the fall-out from
      this changeset.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      6e489f3f
    • L
      Fix broken build · fc5d642f
      Luiz Capitulino 提交于
      The only caller of on_vcpu() is protected by ifdef
      KVM_CAP_SET_GUEST_DEBUG, so protect on_vcpu() too otherwise QEMU
      may not to build.
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      fc5d642f
    • A
      Use Little Endian for Dirty Log · 96c1606b
      Alexander Graf 提交于
      We currently use host endian long types to store information
      in the dirty bitmap.
      
      This works reasonably well on Little Endian targets, because the
      u32 after the first contains the next 32 bits. On Big Endian this
      breaks completely though, forcing us to be inventive here.
      
      So Ben suggested to always use Little Endian, which looks reasonable.
      
      We only have dirty bitmap implemented in Little Endian targets so far
      and since PowerPC would be the first Big Endian platform, we can just
      as well switch to Little Endian always with little effort without
      breaking existing targets.
      
      This is the userspace part of the patch. It shouldn't change anything
      for existing targets, but help PowerPC.
      
      It replaces my older patch called "Use 64bit pointer for dirty log".
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      96c1606b
    • A
      Use 64bit pointer for dirty log · 1c7936e3
      Alexander Graf 提交于
      Dirty logs currently get written with native "long" size. On little endian
      it doesn't matter if we use uint64_t instead though, because we'd still end
      up using the right bytes.
      
      On big endian, this does become a bigger problem, so we need to ensure that
      kernel and userspace talk the same language, which means getting rid of "long"
      and using a defined size instead.
      
      So I decided to use 64 bit types at all times. This doesn't break existing
      targets but will in conjunction with a patch I'll send to the KVM ML make
      dirty logs work with 32 bit userspace on 64 kernel with big endian.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      1c7936e3
  11. 22 7月, 2009 4 次提交
  12. 30 6月, 2009 2 次提交
  13. 17 6月, 2009 1 次提交
    • J
      kvm: Fix IRQ injection into full queue · 8c14c173
      Jan Kiszka 提交于
      User space may only inject interrupts during kvm_arch_pre_run if
      ready_for_interrupt_injection is set in kvm_run. But that field is
      updated on exit from KVM_RUN, so we must ensure that we enter the
      kernel after potentially queuing an interrupt, otherwise we risk to
      loose one - like it happens with the current code against latest
      kernel modules (since kvm-86) that started to queue only a single
      interrupt.
      
      Fix the problem by reordering kvm_cpu_exec.
      
      Credits go to Gleb Natapov for analyzing the issue in details.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      8c14c173
  14. 07 6月, 2009 1 次提交
  15. 22 5月, 2009 6 次提交
  16. 20 5月, 2009 1 次提交
  17. 09 5月, 2009 1 次提交
  18. 01 5月, 2009 2 次提交
  19. 17 4月, 2009 3 次提交
  20. 11 4月, 2009 1 次提交
  21. 13 3月, 2009 1 次提交
    • A
      Guest debugging support for KVM (Jan Kiszka) · e22a25c9
      aliguori 提交于
      This is a backport of the guest debugging support for the KVM
      accelerator that is now part of the KVM tree. It implements the reworked
      KVM kernel API for guest debugging (KVM_CAP_SET_GUEST_DEBUG) which is
      not yet part of any mainline kernel but will probably be 2.6.30 stuff.
      So far supported is x86, but PPC is expected to catch up soon.
      
      Core features are:
       - unlimited soft-breakpoints via code patching
       - hardware-assisted x86 breakpoints and watchpoints
      
      Changes in this version:
       - use generic hook cpu_synchronize_state to transfer registers between
         user space and kvm
       - push kvm_sw_breakpoints into KVMState
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6825 c046a42c-6fe2-441c-8c8c-71466251a162
      e22a25c9
  22. 07 3月, 2009 1 次提交
    • A
      Fix race condition on access to env->interrupt_request · be214e6c
      aurel32 提交于
      env->interrupt_request is accessed as the bit level from both main code
      and signal handler, making a race condition possible even on CISC CPU.
      This causes freeze of QEMU under high load when running the dyntick
      clock.
      
      The patch below move the bit corresponding to CPU_INTERRUPT_EXIT in a
      separate variable, declared as volatile sig_atomic_t, so it should be
      work even on RISC CPU.
      
      We may want to move the cpu_interrupt(env, CPU_INTERRUPT_EXIT) case in
      its own function and get rid of CPU_INTERRUPT_EXIT. That can be done
      later, I wanted to keep the patch short for easier review.
      Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6728 c046a42c-6fe2-441c-8c8c-71466251a162
      be214e6c