1. 20 Aug, 2013 1 commit
  2. 11 Jun, 2013 1 commit
    • Michael Tokarev's avatar
      gitignore: unignore *.patch · f3a22014
      Michael Tokarev authored
      This partially reverts:
      
       commit 082369e6
       Author: liguang <lig.fnst@cn.fujitsu.com>
       Date:   Fri Mar 22 16:44:13 2013 +0800
      
          gitignore: ignore more files
      
      I'm not sure how this went in.  The thing is that
      ignoring *.patch, in my opinion, is just wrong.
      Especially for downstreams who apply patches for
      real.
      Signed-off-by: default avatarMichael Tokarev <mjt@tls.msk.ru>
      f3a22014
  3. 26 Apr, 2013 1 commit
  4. 28 Mar, 2013 2 commits
  5. 22 Mar, 2013 1 commit
  6. 21 Feb, 2013 1 commit
  7. 15 Jan, 2013 1 commit
  8. 08 Jan, 2013 1 commit
  9. 23 Dec, 2012 1 commit
  10. 19 Dec, 2012 1 commit
  11. 18 Dec, 2012 1 commit
  12. 05 Oct, 2012 1 commit
  13. 04 Oct, 2012 1 commit
  14. 07 Jul, 2012 1 commit
    • Eduardo Habkost's avatar
      .gitignore update · eeae63a7
      Eduardo Habkost authored
      Makes sure the following files are ignored:
      
        libcacard/.libs/
        libcacard/libcacard.la
        libcacard/libcacard.pc
        libcacard/libcacard/
        libcacard/osdep.lo
        libcacard/oslib-posix.lo
        libcacard/qemu-thread-posix.lo
        libcacard/qemu-timer-common.lo
        libcacard/trace.lo
        libcacard/trace/
        tests/test-visitor-serialization
        vscclient
      Signed-off-by: default avatarEduardo Habkost <ehabkost@redhat.com>
      Signed-off-by: default avatarBlue Swirl <blauwirbel@gmail.com>
      eeae63a7
  15. 19 Mar, 2012 1 commit
  16. 21 Feb, 2012 1 commit
  17. 18 Feb, 2012 1 commit
  18. 20 Jan, 2012 1 commit
  19. 01 Nov, 2011 1 commit
  20. 30 Oct, 2011 1 commit
  21. 02 Aug, 2011 1 commit
  22. 23 Jul, 2011 1 commit
  23. 16 Apr, 2011 1 commit
  24. 24 Feb, 2011 1 commit
  25. 10 Feb, 2011 1 commit
  26. 21 Nov, 2010 2 commits
    • Daniel P. Berrange's avatar
      Add a DTrace tracing backend targetted for SystemTAP compatability · b3d08c02
      Daniel P. Berrange authored
      This introduces a new tracing backend that targets the SystemTAP
      implementation of DTrace userspace tracing. The core functionality
      should be applicable and standard across any DTrace implementation
      on Solaris, OS-X, *BSD, but the Makefile rules will likely need
      some small additional changes to cope with OS specific build
      requirements.
      
      This backend builds a little differently from the other tracing
      backends. Specifically there is no 'trace.c' file, because the
      'dtrace' command line tool generates a '.o' file directly from
      the dtrace probe definition file. The probe definition is usually
      named with a '.d' extension but QEMU uses '.d' files for its
      external makefile dependancy tracking, so this uses '.dtrace' as
      the extension for the probe definition file.
      
      The 'tracetool' program gains the ability to generate a trace.h
      file for DTrace, and also to generate the trace.d file containing
      the dtrace probe definition.
      
      Example usage of a dtrace probe in systemtap looks like:
      
        probe process("qemu").mark("qemu_malloc") {
          printf("Malloc %d %p\n", $arg1, $arg2);
        }
      
      * .gitignore: Ignore trace-dtrace.*
      * Makefile: Extra rules for generating DTrace files
      * Makefile.obj: Don't build trace.o for DTrace, use
        trace-dtrace.o generated by 'dtrace' instead
      * tracetool: Support for generating DTrace data files
      Reviewed-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Signed-off-by: default avatarDaniel P. Berrange <berrange@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      b3d08c02
    • Anthony Liguori's avatar
      06da6e44
  27. 16 Nov, 2010 1 commit
    • Daniel P. Berrange's avatar
      Add a DTrace tracing backend targetted for SystemTAP compatability · 4addb112
      Daniel P. Berrange authored
      This introduces a new tracing backend that targets the SystemTAP
      implementation of DTrace userspace tracing. The core functionality
      should be applicable and standard across any DTrace implementation
      on Solaris, OS-X, *BSD, but the Makefile rules will likely need
      some small additional changes to cope with OS specific build
      requirements.
      
      This backend builds a little differently from the other tracing
      backends. Specifically there is no 'trace.c' file, because the
      'dtrace' command line tool generates a '.o' file directly from
      the dtrace probe definition file. The probe definition is usually
      named with a '.d' extension but QEMU uses '.d' files for its
      external makefile dependancy tracking, so this uses '.dtrace' as
      the extension for the probe definition file.
      
      The 'tracetool' program gains the ability to generate a trace.h
      file for DTrace, and also to generate the trace.d file containing
      the dtrace probe definition.
      
      Example usage of a dtrace probe in systemtap looks like:
      
        probe process("qemu").mark("qemu_malloc") {
          printf("Malloc %d %p\n", $arg1, $arg2);
        }
      
      * .gitignore: Ignore trace-dtrace.*
      * Makefile: Extra rules for generating DTrace files
      * Makefile.obj: Don't build trace.o for DTrace, use
        trace-dtrace.o generated by 'dtrace' instead
      * tracetool: Support for generating DTrace data files
      Signed-off-by: default avatarDaniel P. Berrange <berrange@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      4addb112
  28. 09 Oct, 2010 1 commit
  29. 09 Sep, 2010 2 commits
    • Stefan Hajnoczi's avatar
      trace: Add simple built-in tracing backend · 26f7227b
      Stefan Hajnoczi authored
      This patch adds a simple tracer which produces binary trace files.  To
      try out the simple backend:
      
      $ ./configure --trace-backend=simple
      $ make
      
      After running QEMU you can pretty-print the trace:
      
      $ ./simpletrace.py trace-events trace.log
      
      The output of simpletrace.py looks like this:
      
        qemu_realloc 0.699 ptr=0x24363f0 size=0x3 newptr=0x24363f0
        qemu_free 0.768 ptr=0x24363f0
        ^           ^---- timestamp delta (us)
        |____ trace event name
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      trace: Make trace record fields 64-bit
      
      Explicitly use 64-bit fields in trace records so that timestamps and
      magic numbers work for 32-bit host builds.
      
      Includes fixes from Prerna Saxena <prerna@linux.vnet.ibm.com>.
      Signed-off-by: default avatarPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      26f7227b
    • Stefan Hajnoczi's avatar
      trace: Add trace-events file for declaring trace events · 94a420b1
      Stefan Hajnoczi authored
      This patch introduces the trace-events file where trace events can be
      declared like so:
      
      qemu_malloc(size_t size) "size %zu"
      qemu_free(void *ptr) "ptr %p"
      
      These trace event declarations are processed by a new tool called
      tracetool to generate code for the trace events.  Trace event
      declarations are independent of the backend tracing system (LTTng User
      Space Tracing, ftrace markers, DTrace).
      
      The default "nop" backend generates empty trace event functions.
      Therefore trace events are disabled by default.
      
      The trace-events file serves two purposes:
      
      1. Adding trace events is easy.  It is not necessary to understand the
         details of a backend tracing system.  The trace-events file is a
         single location where trace events can be declared without code
         duplication.
      
      2. QEMU is not tightly coupled to one particular backend tracing system.
         In order to support tracing across QEMU host platforms and to
         anticipate new backend tracing systems that are currently maturing,
         it is important to be flexible and not tied to one system.
      
      This commit includes fixes from Prerna Saxena
      <prerna@linux.vnet.ibm.com> and Blue Swirl <blauwirbel@gmail.com>.
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      94a420b1
  30. 25 Jul, 2010 1 commit
  31. 01 Jul, 2010 1 commit
  32. 27 Jun, 2010 1 commit
  33. 20 May, 2010 1 commit
  34. 10 Feb, 2010 1 commit
    • Stefan Weil's avatar
      Documentation: Add build support for documentation in pdf format · 20cc9997
      Stefan Weil authored
      Makefile already supported dvi, html and info formats,
      but pdf was missing.
      
      pdf is especially convenient for printing and for
      documentation reviews. I hope it will help to
      improve qemu's documentation.
      
      Make now supports the new target 'pdf' which will
      create qemu-doc.pdf and qemu-tech.pdf. It is also
      possible to build both files individually.
      
      texi2pdf and texi2dvi are rather noisy, so normally
      some less important warnings are suppressed.
      When make is called with V=1 (verbose mode),
      warnings are not suppressed.
      
      The patch also sorts the documentation targets
      alphabetically and wraps a line which was too long.
      Signed-off-by: default avatarStefan Weil <weil@mail.berlios.de>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      20cc9997
  35. 23 Dec, 2009 1 commit
  36. 08 Oct, 2009 2 commits