1. 16 Sep, 2014 1 commit
  2. 11 Sep, 2014 1 commit
  3. 01 Sep, 2014 1 commit
  4. 25 Aug, 2014 2 commits
    • Alexey Kardashevskiy's avatar
      s390x: Migrate to new NMI interface · 3dd7852f
      Alexey Kardashevskiy authored
      This implements an NMI interface for s390 and s390-ccw machines.
      
      This removes #ifdef s390 branch in qmp_inject_nmi so new s390's
      nmi_monitor_handler() callback is going to be used for NMI.
      
      Since nmi_monitor_handler()-calling code is platform independent,
      CPUState::cpu_index is used instead of S390CPU::env.cpu_num.
      There should not be any change in behaviour as both @cpu_index and
      @cpu_num are global CPU numbers.
      
      Note that s390_cpu_restart() already takes care of the specified cpu,
      so we don't need to schedule via async_run_on_cpu().
      
      Since the only error s390_cpu_restart() can return is ENOSYS, convert
      it to QERR_UNSUPPORTED.
      Signed-off-by: default avatarAlexey Kardashevskiy <aik@ozlabs.ru>
      Reviewed-by: default avatarAlexander Graf <agraf@suse.de>
      Reviewed-by: default avatarCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      3dd7852f
    • Alexey Kardashevskiy's avatar
      cpus: Define callback for QEMU "nmi" command · 9cb805fd
      Alexey Kardashevskiy authored
      This introduces an NMI (Non Maskable Interrupt) interface with
      a single nmi_monitor_handler() method. A machine or a device can
      implement it. This searches for an QOM object with this interface
      and if it is implemented, calls it. The callback implements an action
      required to cause debug crash dump on in-kernel debugger invocation.
      The callback returns Error**.
      
      This adds a nmi_monitor_handle() helper which walks through
      all objects to find the interface. The interface method is called
      for all found instances.
      
      This adds support for it in qmp_inject_nmi(). Since no architecture
      supports it at the moment, there is no change in behaviour.
      
      This changes inject-nmi command description for HMP and QMP.
      Signed-off-by: default avatarAlexey Kardashevskiy <aik@ozlabs.ru>
      Reviewed-by: default avatarAlexander Graf <agraf@suse.de>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      9cb805fd
  5. 07 Aug, 2014 1 commit
  6. 06 Aug, 2014 7 commits
  7. 23 Jun, 2014 2 commits
  8. 19 Jun, 2014 1 commit
  9. 17 Jun, 2014 1 commit
  10. 14 May, 2014 1 commit
  11. 27 Apr, 2014 1 commit
  12. 13 Mar, 2014 4 commits
  13. 09 Mar, 2014 1 commit
  14. 11 Feb, 2014 1 commit
  15. 23 Dec, 2013 1 commit
  16. 06 Nov, 2013 1 commit
    • Paolo Bonzini's avatar
      timers: fix stop/cont with -icount · 5f3e3101
      Paolo Bonzini authored
      Stop/cont commands are broken with -icount due to a deadlock.  The
      real problem is that the computation of timers_state.cpu_ticks_offset
      makes no sense with -icount enabled: we set it to an icount clock value
      in cpu_disable_ticks, and subtract a TSC (or similar, whatever
      cpu_get_real_ticks happens to return) value in cpu_enable_ticks.
      
      The fix is simple.  timers_state.cpu_ticks_offset is only used
      together with cpu_get_real_ticks, so we can use cpu_get_real_ticks
      in cpu_disable_ticks.  There is no need to update cpu_ticks_prev
      at the time cpu_disable_ticks is called; instead, we can do it
      the next time cpu_get_ticks is called.
      
      The change to cpu_disable_ticks is the important part of the patch.
      The rest modifies the code to always check timers_state.cpu_ticks_prev,
      even when the ticks are not advancing (i.e. the VM is stopped).  It also
      makes a similar change to cpu_get_clock_locked, so that the code remains
      similar for cpu_get_ticks and cpu_get_clock_locked.
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Message-id: 1382977938-13844-1-git-send-email-pbonzini@redhat.com
      Signed-off-by: default avatarAnthony Liguori <aliguori@amazon.com>
      5f3e3101
  17. 25 Oct, 2013 1 commit
  18. 17 Oct, 2013 6 commits
  19. 03 Sep, 2013 2 commits
  20. 30 Aug, 2013 1 commit
    • Eugene (jno) Dvurechenski's avatar
      s390: wire up nmi command to raise a RESTART interrupt on S390 · 7f7f9752
      Eugene (jno) Dvurechenski authored
      There is the 'nmi' command that is used to trigger a guest dump via kdump feature on x86.
      s390 uses RESTART interrupt to trigger kdump.
      So, this patch provides a mean to use 'nmi' command on s390 to raise RESTART interrupt.
      
      The CPU to receive the RESTART interrupt is the "default" one.
      
      There is an infrastructure to select the "default" CPU using 'cpu' command.
      The 'info cpus' command can be used to see which one is the "default".
      
      In order to wire up the RESTART to 'nmi' command we had to:
      1. implement the kvm_s390_cpu_restart function by exporting the existing code
      2. implement s390_cpu_restart function as kvm-aware wrapper
      3. modify the qmp_inject_nmi function to enable (for s390) the scan for
         "default" CPU and call s390_cpu_restart for it;
      3. fix some messages.
      Signed-off-by: default avatarEugene (jno) Dvurechenski <jno@linux.vnet.ibm.com>
      Signed-off-by: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      Acked-by: default avatarAlexander Graf <agraf@suse.de>
      7f7f9752
  21. 22 Aug, 2013 2 commits
  22. 16 Aug, 2013 1 commit