1. 17 Sep, 2010 5 commits
  2. 16 Sep, 2010 1 commit
  3. 15 Sep, 2010 3 commits
  4. 14 Sep, 2010 1 commit
  5. 13 Sep, 2010 1 commit
  6. 11 Sep, 2010 3 commits
  7. 10 Sep, 2010 6 commits
  8. 09 Sep, 2010 20 commits
    • Andrzej Zaborowski's avatar
      vmware_vga: Replace the few tab-indents with spaces (clean-up). · 9f810beb
      Andrzej Zaborowski authored
      Use 4 spaces instead of 2, too.
      9f810beb
    • Andrzej Zaborowski's avatar
      vmware_vga: Add checks to deal with non-atomic fifo writes. · 4dedc07f
      Andrzej Zaborowski authored
      Janne Huttunen noticed that the FIFO end pointer is updated by the
      guest after writing each word to the FIFO, at least the X.org driver
      which is open does this.  This means that there's no way for the
      host to know if the guest is in the middle a write operation.  Qemu
      thus needs to read the beginning of the command up to when it's able
      to tell how many words are expected for the given command.  It will
      abort reading and rewind the FIFO if there aren't enough words yet,
      this should be relatively rare but it is suspected to have been the
      cause of the occasional FIFO overrun that killed the display.
      4dedc07f
    • Stefan Weil's avatar
      hw/omap: Fix default setup for OMAP UART devices · 6a8aabd3
      Stefan Weil authored
      Character devices created by qemu_chr_open don't
      allow duplicate device names, so naming all
      UART devices "null" no longer works.
      
      Running "qemu-system-arm -M n800" (and some other machines)
      results in this error message:
      
      	qemu-system-arm: Duplicate ID 'null' for chardev
      	Can't create serial device, empty char device
      
      This is fixed by setting a default label "uart1",
      "uart2" or "uart3".
      
      Cc: Andrzej Zaborowski <andrew.zaborowski@intel.com>
      Signed-off-by: default avatarStefan Weil <weil@mail.berlios.de>
      6a8aabd3
    • Prerna Saxena's avatar
    • Prerna Saxena's avatar
      bd3c9aa5
    • Stefan Hajnoczi's avatar
      trace: Trace virtqueue operations · 64979a4d
      Stefan Hajnoczi authored
      This patch adds trace events for virtqueue operations including
      adding/removing buffers, notifying the guest, and receiving a notify
      from the guest.
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      64979a4d
    • Stefan Hajnoczi's avatar
      trace: Trace virtio-blk, multiwrite, and paio_submit · 6d519a5f
      Stefan Hajnoczi authored
      This patch adds trace events that make it possible to observe
      virtio-blk.
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      6d519a5f
    • Stefan Hajnoczi's avatar
      trace: Trace qemu_malloc() and qemu_vmalloc() · cd245a19
      Stefan Hajnoczi authored
      It is often useful to instrument memory management functions in order to
      find leaks or performance problems.  This patch adds trace events for
      the memory allocation primitives.
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      cd245a19
    • Stefan Hajnoczi's avatar
      81a97d9d
    • Stefan Hajnoczi's avatar
      trace: Add LTTng Userspace Tracer backend · 7e24e92a
      Stefan Hajnoczi authored
      This patch adds LTTng Userspace Tracer (UST) backend support.  The UST
      system requires no kernel support but libust and liburcu must be
      installed.
      
      $ ./configure --trace-backend ust
      $ make
      
      Start the UST daemon:
      $ ustd &
      
      List available tracepoints and enable some:
      $ ustctl --list-markers $(pgrep qemu)
      [...]
      {PID: 5458, channel/marker: ust/paio_submit, state: 0, fmt: "acb %p
      opaque %p sector_num %lu nb_sectors %lu type %lu" 0x4b32ba}
      $ ustctl --enable-marker "ust/paio_submit" $(pgrep qemu)
      
      Run the trace:
      $ ustctl --create-trace $(pgrep qemu)
      $ ustctl --start-trace $(pgrep qemu)
      [...]
      $ ustctl --stop-trace $(pgrep qemu)
      $ ustctl --destroy-trace $(pgrep qemu)
      
      Trace results can be viewed using lttv-gui.
      
      More information about UST:
      http://lttng.org/ustSigned-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      trace: Check for LTTng Userspace Tracer headers
      
      When using the 'ust' backend, check if the relevant headers are
      available at host.
      Signed-off-by: default avatarPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      7e24e92a
    • Prerna Saxena's avatar
      trace: Add trace file name command-line option · ab6540d5
      Prerna Saxena authored
      This patch adds an optional command line switch '-trace' to specify the
      filename to write traces to, when qemu starts.
      Eg, If compiled with the 'simple' trace backend,
      [temp@system]$ qemu -trace FILENAME IMAGE
      Allows the binary traces to be written to FILENAME instead of the option
      set at config-time.
      Signed-off-by: default avatarPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      ab6540d5
    • Stefan Hajnoczi's avatar
      trace: Add trace-file command to open/close/flush trace file · c5ceb523
      Stefan Hajnoczi authored
      This patch adds the trace-file command:
      
        trace-file [on|off|flush]
      
        Open, close, or flush the trace file.  If no argument is given,
        the status of the trace file is displayed.
      
      The trace file is turned on by default but is only written out when the
      trace buffer becomes full.  The flush operation can be used to force
      write out at any time.
      
      Turning off the trace file does not change the state of trace events;
      tracing will continue to the trace buffer.  When the trace file is off,
      use "info trace" to display the contents of the trace buffer in memory.
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      This commit also contains the trace-file sub-command from the following
      commit:
      
      commit 5ce8d1a957afae2c52ad748944ce72848ccf57bd
      Author: Prerna Saxena <prerna@linux.vnet.ibm.com>
      Date:   Wed Aug 4 16:23:54 2010 +0530
      
          trace: Add options to specify trace file name at startup and runtime
      
          This patch adds an optional command line switch '-trace' to specify the
          filename to write traces to, when qemu starts.
          Eg, If compiled with the 'simple' trace backend,
          [temp@system]$ qemu -trace FILENAME IMAGE
          Allows the binary traces to be written to FILENAME instead of the option
          set at config-time.
      
          Also, this adds monitor sub-command 'set' to trace-file commands to
          dynamically change trace log file at runtime.
          Eg,
          (qemu)trace-file set FILENAME
          This allows one to set trace outputs to FILENAME from the default
          specified at startup.
      Signed-off-by: default avatarPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      c5ceb523
    • Prerna Saxena's avatar
      trace: Specify trace file name · 9410b56c
      Prerna Saxena authored
      Allow users to specify a file for trace-outputs at configuration.
      Also, allow trace files to be annotated by <pid> so each qemu instance has
      unique traces.
      
      The trace file name can be passed as a config option:
      --trace-file=/path/to/file
      (Default: trace )
      At runtime, the pid of the qemu process is appended to the filename so
      that mutiple qemu instances do not have overlapping logs.
      
      Eg : trace-1234 for qemu launched with pid 1234.
      
      I have yet to test this on windows. getpid() is used at many places
      in code(including vnc.c), so I'm hoping this would be okay too.
      Edited-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      9410b56c
    • Stefan Hajnoczi's avatar
      trace: Support disabled events in trace-events · 1e2cf2bc
      Stefan Hajnoczi authored
      Sometimes it is useful to disable a trace event.  Removing the event
      from trace-events is not enough since source code will call the
      trace_*() function for the event.
      
      This patch makes it easy to build without specific trace events by
      marking them disabled in trace-events:
      
      disable multiwrite_cb(void *mcb, int ret) "mcb %p ret %d"
      
      This builds without the multiwrite_cb trace event.
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      trace: Allow bulk enabling/disabling of trace events at compile time
      
      For 'simple' trace backend, allow bulk enabling/disabling of trace
      events at compile time.  Trace events that are preceded by 'disable'
      keyword are compiled in, but turned off by default. These can
      individually be turned on using the monitor.  All other trace events are
      enabled by default.
      
      TODO :
      This could be enhanced when the trace-event namespace is partitioned into a
      group and an ID within that group. In such a case, marking a group as enabled
      would automatically enable all trace-events listed under it.
      Signed-off-by: default avatarPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      1e2cf2bc
    • Prerna Saxena's avatar
      trace: Support for dynamically enabling/disabling trace events · 22890ab5
      Prerna Saxena authored
      This patch adds support for dynamically enabling/disabling of trace events.
      This is done by internally maintaining each trace event's state, and
      permitting logging of data from a trace event only if it is in an
      'active' state.
      
      Monitor commands added :
      1) info trace-events 		: to view all available trace events and
      				  their state.
      2) trace-event NAME on|off 	: to enable/disable data logging from a
      				  given trace event.
      				  Eg, trace-event paio_submit off
      				  	disables logging of data when
      					paio_submit is hit.
      
      By default, all trace-events are disabled. One can enable desired trace-events
      via the monitor.
      Signed-off-by: default avatarPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      trace: Monitor command 'info trace'
      
      Monitor command 'info trace' to display contents of trace buffer
      Signed-off-by: default avatarPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      trace: Remove monitor.h dependency from simpletrace
      
      User-mode targets don't have a monitor so the simple trace backend
      currently does not build on those targets.  This patch abstracts the
      monitor printing interface so there is no direct coupling between
      simpletrace and the monitor.
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      22890ab5
    • 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
    • Edgar E. Iglesias's avatar
      ef9d48da
    • Stefan Weil's avatar
      elf: Calculate symbol size if needed · e403e433
      Stefan Weil authored
      Symbols with a size of 0 are unusable for the disassembler.
      
      Example:
      
      While running an arm linux kernel, no symbolic names are
      used in qemu.log when the cpu is executing an assembler function.
      
      Assume that the size of such symbols is the difference to the
      next symbol value.
      Signed-off-by: default avatarStefan Weil <weil@mail.berlios.de>
      Signed-off-by: default avatarBlue Swirl <blauwirbel@gmail.com>
      e403e433
    • Blue Swirl's avatar
      Fix OpenBSD build warning · d7d9b528
      Blue Swirl authored
      Fix this warning:
        CC    savevm.o
      /src/qemu/savevm.c: In function `do_savevm':
      /src/qemu/savevm.c:1900: warning: passing arg 1 of `localtime_r' from incompatible pointer type
      
      It looks like on OpenBSD the type of tv_sec in struct timeval is still
      'long' instead of time_t as in most other OS. Fix by adding a cast.
      Signed-off-by: default avatarBlue Swirl <blauwirbel@gmail.com>
      d7d9b528