1. 01 2月, 2017 2 次提交
  2. 12 10月, 2016 2 次提交
  3. 06 10月, 2016 1 次提交
    • P
      rules.mak: quiet-command: Split command name and args to print · 0bdb12c7
      Peter Maydell 提交于
      The quiet-command make rule currently takes two arguments:
      the command and arguments to run, and a string to print if
      the V flag is not set (ie we are not being verbose).
      By convention, the string printed is of the form
      "  NAME   some args". Unfortunately to get nicely lined up
      output all the strings have to agree about what column the
      arguments should start in, which means that if we add a
      new quiet-command usage which wants a slightly longer CMD
      name then we either put up with misalignment or change
      every quiet-command string.
      
      Split the quiet-mode string into two, the "NAME" and
      the "same args" part, and use printf(1) to format the
      string automatically. This means we only need to change
      one place if we want to support a longer maximum name.
      
      In particular, we can now print 7-character names lined
      up properly (they are needed for the OSX "SETTOOL" invocation).
      
      Change all the uses of quiet-command to the new syntax.
      (Any which are missed or inadvertently reintroduced
      via later merges will result in slightly misformatted
      quiet output rather than disaster.)
      
      A few places in the pc-bios/ makefiles are updated to use
      "BUILD", "SIGN" and "STRIP" rather than "Building",
      "Signing" and "Stripping" for consistency and to keep them
      below 7 characters. Module .mo links now print "LD" rather
      than the nonstandard "LD -r".
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Message-id: 1475598441-27908-1-git-send-email-peter.maydell@linaro.org
      0bdb12c7
  4. 19 7月, 2016 1 次提交
  5. 21 6月, 2016 1 次提交
  6. 07 1月, 2016 2 次提交
    • S
      trace: add make dependencies on tracetool source · cef517ca
      Stefan Hajnoczi 提交于
      Patches that change tracetool can break the build if old build output
      files are lying around.
      
      This happens because the Makefile does not specify dependencies on
      tracetool.  The build will use old object files that do not match the
      current source code.
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      cef517ca
    • S
      trace: fix make foo-timestamp rules · 9967e4fe
      Stefan Hajnoczi 提交于
      The Makefile uses intermediate timestamp files to avoid rebuilding if
      tracetool output is unchanged.
      
      Timestamps are implemented incorrectly.  This was fixed for rules.mak in
      commit 4b25966a ("rules.mak: cleanup
      config generation rules") but never fixed in trace/Makefile.objs.
      
      The problem with the old timestamp implementation was that make doesn't
      notice the updated file modification time until the next time it is run.
      It was necessary to run make twice in a row to achieve a full rebuild.
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      9967e4fe
  7. 26 9月, 2014 1 次提交
  8. 09 9月, 2014 1 次提交
  9. 12 8月, 2014 4 次提交
  10. 09 6月, 2014 1 次提交
    • L
      trace: Multi-backend tracing · 5b808275
      Lluís Vilanova 提交于
      Adds support to compile QEMU with multiple tracing backends at the same time.
      
      For example, you can compile QEMU with:
      
        $ ./configure --enable-trace-backends=ftrace,dtrace
      
      Where 'ftrace' can be handy for having an in-flight record of events, and 'dtrace' can be later used to extract more information from the system.
      
      This patch allows having both available without recompiling QEMU.
      Signed-off-by: NLluís Vilanova <vilanova@ac.upc.edu>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      5b808275
  11. 08 5月, 2014 1 次提交
  12. 19 2月, 2014 1 次提交
  13. 03 5月, 2013 1 次提交
    • E
      trace: Add ftrace tracing backend · 781e9545
      Eiichi Tsukata 提交于
      This patch adds a ftrace tracing backend which sends trace event to
      ftrace marker file. You can effectively compare qemu trace data and
      kernel(especially, kvm.ko when using KVM) trace data.
      The ftrace backend is restricted to Linux only.
      
      To try out the ftrace backend:
      
       $ ./configure --trace-backend=ftrace
       $ make
      
      if you use KVM, enable kvm events in ftrace:
      
       # sudo echo 1 > /sys/kernel/debug/tracing/events/kvm/enable
      
      After running qemu by root user, you can get the trace:
      
       # cat /sys/kernel/debug/tracing/trace
      Signed-off-by: NEiichi Tsukata <eiichi.tsukata.xh@hitachi.com>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      781e9545
  14. 28 3月, 2013 2 次提交
  15. 30 1月, 2013 1 次提交
  16. 13 1月, 2013 3 次提交
  17. 24 12月, 2012 1 次提交