Skip to content
Snippets Groups Projects
  1. Jun 01, 2023
  2. Dec 21, 2022
  3. Oct 06, 2022
  4. Feb 09, 2022
  5. Oct 05, 2021
  6. Jul 10, 2021
  7. Jun 02, 2021
  8. Sep 09, 2020
  9. Oct 28, 2019
  10. Sep 25, 2019
  11. Aug 21, 2019
  12. Jun 17, 2019
  13. Mar 22, 2019
  14. Jan 25, 2019
  15. Aug 31, 2018
    • John Snow's avatar
      jobs: remove ret argument to job_completed; privatize it · 404ff28d
      John Snow authored
      
      Jobs are now expected to return their retcode on the stack, from the
      .run callback, so we can remove that argument.
      
      job_cancel does not need to set -ECANCELED because job_completed will
      update the return code itself if the job was canceled.
      
      While we're here, make job_completed static to job.c and remove it from
      job.h; move the documentation of return code to the .run() callback and
      to the job->ret property, accordingly.
      
      Signed-off-by: default avatarJohn Snow <jsnow@redhat.com>
      Message-id: 20180830015734.19765-9-jsnow@redhat.com
      Reviewed-by: default avatarMax Reitz <mreitz@redhat.com>
      Signed-off-by: default avatarMax Reitz <mreitz@redhat.com>
      404ff28d
  16. May 23, 2018
  17. Mar 20, 2018
  18. Mar 19, 2018
    • Peter Xu's avatar
      qmp: support out-of-band (oob) execution · cf869d53
      Peter Xu authored
      
      Having "allow-oob":true for a command does not mean that this command
      will always be run in out-of-band mode.  The out-of-band quick path will
      only be executed if we specify the extra "run-oob" flag when sending the
      QMP request:
      
          { "execute":   "command-that-allows-oob",
            "arguments": { ... },
            "control":   { "run-oob": true } }
      
      The "control" key is introduced to store this extra flag.  "control"
      field is used to store arguments that are shared by all the commands,
      rather than command specific arguments.  Let "run-oob" be the first.
      
      Note that in the patch I exported qmp_dispatch_check_obj() to be used to
      check the request earlier, and at the same time allowed "id" field to be
      there since actually we always allow that.
      
      Reviewed-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      Signed-off-by: default avatarPeter Xu <peterx@redhat.com>
      Message-Id: <20180309090006.10018-19-peterx@redhat.com>
      Reviewed-by: default avatarEric Blake <eblake@redhat.com>
      [eblake: rebase to qobject_to(), spelling fix]
      Signed-off-by: default avatarEric Blake <eblake@redhat.com>
      cf869d53
    • Peter Xu's avatar
      monitor: let suspend/resume work even with QMPs · e3e977d4
      Peter Xu authored
      
      This patches allows QMP monitors to be suspended/resumed.
      
      One thing to mention is that for QMPs that are using IOThreads, we need
      an explicit kick for the IOThread in case it is sleeping.
      
      Meanwhile, we need to take special care on non-interactive HMPs.
      Currently only gdbserver is using that.  For these monitors, we still
      don't allow suspend/resume operations.
      
      Since at it, add traces for the operations.
      
      Signed-off-by: default avatarPeter Xu <peterx@redhat.com>
      Message-Id: <20180309090006.10018-14-peterx@redhat.com>
      Reviewed-by: default avatarEric Blake <eblake@redhat.com>
      Signed-off-by: default avatarEric Blake <eblake@redhat.com>
      e3e977d4
  19. Mar 12, 2018
  20. Feb 19, 2018
    • Stefan Hajnoczi's avatar
      trace: avoid SystemTap "char const" warnings · 7f1d87ab
      Stefan Hajnoczi authored
      SystemTap's dtrace(1) produces the following warning when it encounters
      "char const" instead of "const char":
      
        Warning: /usr/bin/dtrace:trace-dtrace-root.dtrace:66: syntax error near:
        probe flatview_destroy_rcu
      
        Warning: Proceeding as if --no-pyparsing was given.
      
      This is a limitation in current SystemTap releases.  I have sent a patch
      upstream to accept "char const" since it is valid C:
      
        https://sourceware.org/ml/systemtap/2018-q1/msg00017.html
      
      
      
      In QEMU we still wish to avoid warnings in the current SystemTap
      release.  It's simple enough to replace "char const" with "const char".
      
      I'm not changing the documentation or implementing checks to prevent
      this from occurring again in the future.  The next release of SystemTap
      will hopefully resolve this issue.
      
      Cc: Daniel P. Berrange <berrange@redhat.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      Reviewed-by: default avatarDaniel P. Berrange <berrange@redhat.com>
      Message-id: 20180201162625.4276-1-stefanha@redhat.com
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      7f1d87ab
  21. Jan 16, 2018
  22. Dec 18, 2017
  23. Sep 21, 2017
  24. Aug 01, 2017
  25. Jul 17, 2017
    • Lluís Vilanova's avatar
      trace: [trivial] Statically enable all guest events · 5caa262f
      Lluís Vilanova authored
      The existing optimizations makes it feasible to have them available on all
      builds.
      
      Some quick'n'dirty numbers with 400.perlbench (SPECcpu2006) on the train input
      (medium size - suns.pl) and the guest_mem_before event:
      
      * vanilla, statically disabled
      real    0m2,259s
      user    0m2,252s
      sys     0m0,004s
      
      * vanilla, statically enabled (overhead: 2.18x)
      real    0m4,921s
      user    0m4,912s
      sys     0m0,008s
      
      * multi-tb, statically disabled (overhead: 0.99x) [within noise range]
      real    0m2,228s
      user    0m2,216s
      sys     0m0,008s
      
      * multi-tb, statically enabled (overhead: 0.99x) [within noise range]
      real    0m2,229s
      user    0m2,224s
      sys     0m0,004s
      
      Now enabling all events when booting an ARM system that immediately shuts down
      (https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg04085.html):
      
      * vanilla, statically disabled
      real	0m32,153s
      user	0m31,276s
      sys	0m0,108s
      
      * vanilla, statically enabled (overhead: 1.35x)
      real	0m43,507s
      user	0m42,680s
      sys	0m0,168s
      
      * multi-tb, statically disabled (overhead: 1.03x)
      real	0m32,993s
      user	0m32,516s
      sys	0m0,104s
      
      * multi-tb, statically enabled (overhead: 1.00x) [within noise range]
      real	0m32,110s
      user	0m31,176s
      sys	0m0,156s
      
      And finally enabling all events using Emilio's dbt-bench
      (where orig == vanilla, new == multi-tb):
      
                                                              NBench score; higher is better
      
        180 +-+--------+----------+----------+---------+----------+----------+----------+----------+----------+---------+----------+--------+-+
            |                                                                                                                                 |
            |                                      *** $$$$%%                                                                    orig         |
        160 +-+....................................*.*.$..$.%............................................................orig-enabled       +-+
            |                                      * * $  $ %                                                                     new         |
        140 +-+....................................*.*.$..$.%............................................................new-disabled.......+-+
            |                                      * * $  $ %                                                                                 |
            |                                      * * $  $ %                                                                                 |
        120 +-+....................................*.*.$..$.%...............................................................................+-+
            |                                      * * $  $ %                                                                                 |
            |                                      * * $  $ %                                                                                 |
        100 +-+....................................*.*.$..$.%.....$$$%%%....................................................................+-+
            |                                      * * $  $ % *** $ $  % *** $$$%%                                                            |
         80 +-+....................................*.*.$..$.%.*.*.$.$..%.*.*.$.$.%..........................................................+-+
            |                                      * * $  $ % * * $ $  % * * $ $ %                                                            |
            |                                      * * $  $ % * * $ $  % * * $ $ %                                                            |
         60 +-+.........................***..$$$%%.*.*##..$.%.*.*.$.$..%.*.*.$.$.%..***.$$$%%...............................................+-+
            |                **** $$$%% * *  $ $ % * * #  $ % * *## $  % * * $ $ %  * * $ $ %                                                 |
            |                *  * $ $ % * *  $ $ % * * #  $ % * * # $  % * *## $ %  * * $ $ %                                                 |
         40 +-+..............*..*.$.$.%.*.*..$.$.%.*.*.#..$.%.*.*.#.$..%.*.*.#.$.%..*.*.$.$.%...............................................+-+
            |                *  * $ $ % * *  $ $ % * * #  $ % * * # $  % * * # $ %  * *## $ %                                  *** $$$%%%     |
         20 +-+....***.$$$%%.*..*##.$.%.*.*###.$.%.*.*.#..$.%.*.*.#.$..%.*.*.#.$.%..*.*.#.$.%..................................*.*.$.$..%...+-+
            |      * *## $ % *  * # $ % * *  # $ % * * #  $ % * * # $  % * * # $ %  * * # $ %                                  * *## $  %     |
            |      * * # $ % *  * # $ % * *  # $ % * * #  $ % * * # $  % * * # $ %  * * # $ %            ***###$$%% ***##$$$%% * * # $  %     |
          0 +-+----***##$$%%-****##$$%%-***###$$%%-***##$$$%%-***##$$%%%-***##$$%%--***##$$%%-****##$$%%-***###$$%%-***##$$$%%-***##$$%%%---+-+
           NUMERIC SORTSTRING SORT   BITFIEFP EMULATION ASSIGNMENT       IDEA    HUFFMAN    FOURIER NEURLU DECOMPOSITION      gmean
      png: http://imgur.com/a/8XG5S
      
      
      
      Signed-off-by: default avatarLluís Vilanova <vilanova@ac.upc.edu>
      Reviewed-by: default avatarEmilio G. Cota <cota@braap.org>
      Signed-off-by: default avatarEmilio G. Cota <cota@braap.org>
      Message-id: 149915849243.6295.4484103824675839071.stgit@frigg.lan
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      5caa262f
  26. Jun 15, 2017
  27. Jun 13, 2017
  28. Jun 06, 2017
  29. Jun 02, 2017
  30. May 23, 2017
    • Eric Blake's avatar
      shutdown: Add source information to SHUTDOWN and RESET · cf83f140
      Eric Blake authored
      
      Time to wire up all the call sites that request a shutdown or
      reset to use the enum added in the previous patch.
      
      It would have been less churn to keep the common case with no
      arguments as meaning guest-triggered, and only modified the
      host-triggered code paths, via a wrapper function, but then we'd
      still have to audit that I didn't miss any host-triggered spots;
      changing the signature forces us to double-check that I correctly
      categorized all callers.
      
      Since command line options can change whether a guest reset request
      causes an actual reset vs. a shutdown, it's easy to also add the
      information to reset requests.
      
      Signed-off-by: default avatarEric Blake <eblake@redhat.com>
      Acked-by: David Gibson <david@gibson.dropbear.id.au> [ppc parts]
      Reviewed-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> [SPARC part]
      Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com> [s390x parts]
      Message-Id: <20170515214114.15442-5-eblake@redhat.com>
      Reviewed-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: default avatarMarkus Armbruster <armbru@redhat.com>
      cf83f140
Loading