Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 06 9月, 2016 1 次提交
  3. 21 6月, 2016 1 次提交
  5. 31 3月, 2016 1 次提交
  7. 01 3月, 2016 2 次提交
  9. 09 10月, 2015 1 次提交
  11. 18 11月, 2014 1 次提交
  13. 26 9月, 2014 1 次提交
  15. 12 8月, 2014 1 次提交
  17. 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
  19. 19 2月, 2014 1 次提交
  21. 14 6月, 2013 1 次提交
  23. 03 5月, 2013 1 次提交
  25. 28 3月, 2013 1 次提交
  27. 06 2月, 2013 1 次提交
  29. 16 11月, 2012 2 次提交
  31. 12 3月, 2012 2 次提交
  33. 01 11月, 2011 1 次提交
  35. 21 9月, 2011 2 次提交
  37. 17 9月, 2011 1 次提交
    • S
      trace: allow PRI*64 at beginning and ending of format string · 913540a3
      由 Stefan Hajnoczi 提交于 
      The tracetool parser only picks up PRI*64 and other format string macros
when enclosed between double quoted strings.  Lift this restriction by
extracting everything after the closing ')' as the format string:

  cpu_set_apic_base(uint64_t val) "%016"PRIx64
                                  ^^        ^^

One trick here: it turns out that backslashes in the format string like
"\n" were being interpreted by echo(1).  Fix this by using the POSIX
printf(1) command instead.  Although it normally does not make sense to
include backslashes in trace event format strings, an injected newline
causes tracetool to emit a broken header file and I want to eliminate
cases where broken output is emitted, even if the input was bad.
Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      913540a3
  39. 01 9月, 2011 6 次提交
  41. 26 4月, 2011 2 次提交
  43. 07 3月, 2011 2 次提交
    • S
      simpletrace: Thread-safe tracing · 0b5538c3
      由 Stefan Hajnoczi 提交于 
      Trace events outside the global mutex cannot be used with the simple
trace backend since it is not thread-safe.  There is no check to prevent
them being enabled so people sometimes learn this the hard way.

This patch restructures the simple trace backend with a ring buffer
suitable for multiple concurrent writers.  A writeout thread empties the
trace buffer when threshold fill levels are reached.  Should the
writeout thread be unable to keep up with trace generation, records will
simply be dropped.

Each time events are dropped a special record is written to the trace
file indicating how many events were dropped.  The event ID is
0xfffffffffffffffe and its signature is dropped(uint32_t count).
Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      0b5538c3
    • S
      docs: Update stderr and simple backend, add systemtap backend · b48c20f7
      由 Stefan Hajnoczi 提交于 
      The following additions to the tracing documentation are included:

1. Move "stderr" backend documentation to top-level and out of "simple"
   backend.  Include hints on when this backend is useful.

2. Document the "simple" backend thread-safety limitation.

3. Document the "dtrace" backend for SystemTap.
Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      b48c20f7
  45. 30 1月, 2011 1 次提交
  47. 21 10月, 2010 1 次提交
  49. 09 10月, 2010 1 次提交
  51. 10 9月, 2010 1 次提交