1. 20 2月, 2014 1 次提交
    • F
      rules.mak: introduce DSO rules · 17969268
      Fam Zheng 提交于
      Add necessary rules and flags for shared object generation.
      The new rules introduced here are:
      
      1) %.o in $(common-obj-m) is compiled to %.o, then linked to %.so.
      
      2) %.mo in $(common-obj-m) is the placeholder for %.so for pattern
      matching in Makefile. It's linked to "-shared" with all its dependencies
      (multiple *.o) as input. Which means the list of depended objects must
      be specified in each sub-Makefile.objs:
      
          foo.mo-objs := bar.o baz.o qux.o
      
      in the same style with foo.o-cflags and foo.o-libs. The objects here
      will be prefixed with "$(obj)/" if it's a subdirectory Makefile.objs.
      
      3) For all files ending up in %.so, the following is added automatically:
      
          foo.o-cflags += -fPIC -DBUILD_DSO
      
      Also introduce --enable-modules in configure, the option will enable
      support of shared object build. Otherwise objects are static linked to
      executables.
      Signed-off-by: NFam Zheng <famz@redhat.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      17969268
  2. 15 2月, 2014 1 次提交
    • M
      gitignore: anchor all ignored names · 5556332a
      Michael Tokarev 提交于
      by default, patterns/names in .gitignore are applied
      recursively to all subdirectories.  So any name mentioned
      in .gitignore is ignored in all subdirectores.  This is good
      for, say. object files (*.o), but not good for particular
      names which should be ignored only in one directory.  For
      example, qemu-img.1 file is generated in the top directory,
      and it should be ignored only there, not in some subdir.
      
      At first, this might not matter much, but we have lots of
      examples already where it actually does not help at all.
      For example, top-level .gitignore ignores a file/dir named
      "patches" (which is very questionable by itself), but it
      is applied recursively, so git also ignores, for example,
      debian/patches/ which should not be ignored.
      
      So anchor all the names where appropriate.  .gitignore
      should be cleaned up further, which will be addressed in
      a subsequent patch.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      5556332a
  3. 03 12月, 2013 1 次提交
  4. 26 10月, 2013 1 次提交
  5. 10 9月, 2013 1 次提交
  6. 20 8月, 2013 2 次提交
  7. 12 6月, 2013 1 次提交
    • M
      gitignore: unignore *.patch · f3a22014
      Michael Tokarev 提交于
      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: NMichael Tokarev <mjt@tls.msk.ru>
      f3a22014
  8. 27 4月, 2013 1 次提交
  9. 28 3月, 2013 2 次提交
  10. 22 3月, 2013 1 次提交
  11. 21 2月, 2013 1 次提交
  12. 15 1月, 2013 1 次提交
  13. 09 1月, 2013 1 次提交
  14. 24 12月, 2012 1 次提交
  15. 19 12月, 2012 2 次提交
  16. 06 10月, 2012 1 次提交
  17. 05 10月, 2012 1 次提交
  18. 07 7月, 2012 1 次提交
    • E
      .gitignore update · eeae63a7
      Eduardo Habkost 提交于
      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: NEduardo Habkost <ehabkost@redhat.com>
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      eeae63a7
  19. 19 3月, 2012 1 次提交
  20. 21 2月, 2012 1 次提交
  21. 18 2月, 2012 1 次提交
  22. 21 1月, 2012 1 次提交
  23. 02 11月, 2011 1 次提交
  24. 30 10月, 2011 1 次提交
  25. 02 8月, 2011 1 次提交
  26. 23 7月, 2011 1 次提交
  27. 16 4月, 2011 1 次提交
  28. 25 2月, 2011 1 次提交
  29. 11 2月, 2011 1 次提交
  30. 21 11月, 2010 2 次提交
    • D
      Add a DTrace tracing backend targetted for SystemTAP compatability · b3d08c02
      Daniel P. Berrange 提交于
      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: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      b3d08c02
    • A
      Revert "Add a DTrace tracing backend targetted for SystemTAP compatability" · 06da6e44
      Anthony Liguori 提交于
      This reverts commit 4addb112.
      06da6e44
  31. 16 11月, 2010 1 次提交
    • D
      Add a DTrace tracing backend targetted for SystemTAP compatability · 4addb112
      Daniel P. Berrange 提交于
      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: NDaniel P. Berrange <berrange@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      4addb112
  32. 09 10月, 2010 1 次提交
  33. 10 9月, 2010 2 次提交
    • S
      trace: Add simple built-in tracing backend · 26f7227b
      Stefan Hajnoczi 提交于
      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: NStefan 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: NPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      26f7227b
    • S
      trace: Add trace-events file for declaring trace events · 94a420b1
      Stefan Hajnoczi 提交于
      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: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      94a420b1
  34. 25 7月, 2010 1 次提交
  35. 02 7月, 2010 1 次提交