On 09/14/2011 10:51 AM, Stefan Hajnoczi wrote:
On Tue, Sep 13, 2011 at 8:38 PM, William Cohen wco...@redhat.com wrote:
On 09/13/2011 12:10 PM, William Cohen wrote:
Should the qemu.kvm.cpu_in and qemu.kvm.cpu_out match up? There are a lot
more qemu.kvm.cpu_out than qemu.kvm.cpu_in count.
I
You are correct. the qemu.spec file is doing the copy.
** Changed in: qemu
Status: New = Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/848571
Title:
qemu does not generate a
On 09/13/2011 06:03 AM, Stefan Hajnoczi wrote:
On Mon, Sep 12, 2011 at 4:33 PM, William Cohen wco...@redhat.com wrote:
The RHEL-6 version of qemu-kvm makes the tracepoints available to SystemTap.
I have been working on useful examples for the SystemTap tracepoints in
qemu. There doesn't seem
On 09/13/2011 12:10 PM, William Cohen wrote:
Should the qemu.kvm.cpu_in and qemu.kvm.cpu_out match up? There are a lot
more qemu.kvm.cpu_out than qemu.kvm.cpu_in count.
I found that cpu_in and cpu_out refer to input and output instructions. I
wrote a little script tally up the input
Hi All,
The RHEL-6 version of qemu-kvm makes the tracepoints available to SystemTap. I
have been working on useful examples for the SystemTap tracepoints in qemu.
There doesn't seem to be a great number of examples showing the utility of the
tracepoints in diagnosing problems. However, I came
Public bug reported:
To make the systemtap probing easier to use qemu generates qemu*.stp
files with aliases for various events for each of the executables. The
installer places these files in /usr/share/systemtap/tapset/. These
files are generated by the tracetool. However, the
