de from tracetool/backend/common.py
- Define SDT_USE_VARIADIC in genrated-tracers.h in order to avoid
compilation error when enabling dtrace and ust simultaneously
- Revert tracetool.backend.dtrace.{d(),stap()} back
- Change multi.c:trace_backend_init() to figure out what is wrong when
*_backe
(2014/02/04 18:02), Stefan Hajnoczi wrote:> On Tue, Feb 04, 2014 at 02:26:13PM
+0900, Kazuya Saito wrote:
>> > (2014/01/31 19:37), Stefan Hajnoczi wrote:> On Tue, Jan 28, 2014 at
>> > 01:35:20PM +0900, Kazuya Saito wrote:
>>>> > >> def h(events):
(2014/01/31 19:37), Stefan Hajnoczi wrote:> On Tue, Jan 28, 2014 at 01:35:20PM
+0900, Kazuya Saito wrote:
>
> Okay, more feedback after looking at the rest of the patch.
Thank you for the feedback.
> I think "ust" backend support will simplify the patch a little (see
>
(2014/01/31 6:00), Stefan Hajnoczi wrote:> On Tue, Jan 28, 2014 at 01:35:20PM
+0900, Kazuya Saito wrote:
>
> Some initial comments, I will continue reviewing tomorrow.
Thank you for your comment.
>> This patch implements "multi tracing backend" which enables s
tracing backend. However, we can select ftrace, dtrace, stderr,
simple when selecting more than two backends. Though it's
needless to say about nop, I excluded ust backend because I didn't
test it since it doesn't support LTTng 2.x.
Signed-off-by: Kazuya Saito
This patch enable us to know exit reason of KVM_RUN. It will help us
know where the trouble is caused.
Signed-off-by: Kazuya Saito
---
kvm-all.c|1 +
trace-events |2 ++
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index fdb099c..325f5e7
This patch adds tracepoints at ioctl to kvm. Tracing these ioctl is
useful for clarification whether the cause of troubles is qemu or kvm.
Signed-off-by: Kazuya Saito
---
kvm-all.c|4
trace-events |5 +
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/kvm
_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints.
Add cpu_index to kvm_vcpu_ioctl, kvm_run_exit tracepoints.
Kazuya Saito (2):
kvm-all: add kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints
kvm-all: add kvm_run_exit tracepoint
kvm-all.c|5 +
trace-events |7 +++
2 files changed,
(2013/03/27 20:03), Andreas Färber wrote:> Am 22.03.2013 09:29, schrieb Kazuya
Saito:
>> This patch adds tracepoints at creating and removing virtual
>> devices. It is useful for investigation of trouble related to virtual
>> devices.
>>
>> Signed-off-by: Kazuya
(2013/03/27 17:45), Paolo Bonzini wrote:>
>>> Wouldn't you get the same information from the command line?
>>
>> I think the information you said is different from what I meant. The
>> information I wanted to know is whether QEMU creates/deletes a device
>> successfully or not.
>
> Failing to creat
(2013/03/26 16:15), Paolo Bonzini wrote:
> Il 26/03/2013 08:13, Kazuya Saito ha scritto:
>>>>
>>>> I'm not sure 4-5 are that useful, but the first 3 patches are definitely
>>>> good stuff.
>> Thanks. I'll modify the patch you pointed out
(2013/03/22 20:13), Paolo Bonzini wrote:
> Il 22/03/2013 09:25, Kazuya Saito ha scritto:
>> This series adds tracepoints for helping us clarify the cause of
>> troubles. Virtualization on Linux is composed of some components such
>> as qemu, kvm, libvirt, and so on. So it
This patch adds tracepoints at device-add command. It enables us to
clarify whether the trouble is caused by hot-plug through commands of
virsh (libvirt).
Signed-off-by: Kazuya Saito
---
qdev-monitor.c |2 ++
trace-events |3 +++
2 files changed, 5 insertions(+), 0 deletions(-)
diff
This patch adds tracepoints at creating and removing virtual
devices. It is useful for investigation of trouble related to virtual
devices.
Signed-off-by: Kazuya Saito
---
hw/qdev.c|3 +++
trace-events |4
2 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/hw/qdev.c
This patch enable us to know exit reason of KVM_RUN. It will help us
know where the trouble is caused.
Signed-off-by: Kazuya Saito
---
kvm-all.c|1 +
trace-events |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index da15623..29fca13 100644
This patch adds tracepoints at ioctl to kvm. Tracing these ioctl is
useful for clarification whether the cause of troubles is qemu or kvm.
Signed-off-by: Kazuya Saito
---
kvm-all.c|4
trace-events |5 +
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/kvm
This patch enables us to know RunState transition. It will be userful
for investigation when the trouble occured in special event such like
live migration, shutdown, suspend, and so on.
Signed-off-by: Kazuya Saito
---
trace-events |1 +
vl.c |2 +-
2 files changed, 2 insertions
nce, we've found out they must be useful
for an investigation in the future. Without those tracepoints,
we had a really hard time investigating a problem since the problem's
reproducibility was quite low and there was no clue in the dump of
qemu.
Kazuya Saito (5):
vl: add runstate_set
Signed-off-by: Kazuya Saito
---
include/migration/migration.h |2 ++
migration.c | 19 +--
trace-events |3 +++
3 files changed, 18 insertions(+), 6 deletions(-)
diff --git a/include/migration/migration.h b/include/migration
Signed-off-by: Kazuya Saito
---
trace-events |1 +
vl.c |2 +-
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/trace-events b/trace-events
index 1011f27..bf508f0 100644
--- a/trace-events
+++ b/trace-events
@@ -472,6 +472,7 @@ scsi_request_sense(int target, int lun
ease take it in.
[1]: http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg01198.html
[2]: http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg00775.html
Kazuya Saito (2):
vl: add trace_runstate_set()
migration: add migrate_set_state(), add trace_migrate_set_state()
include/migrat
This patch enables us to know state of migration (MigrationState.state)
transition. We added migstate_set() to make it easier to trace state
transition, and added a tracepoint in this function.
Signed-off-by: Kazuya Saito
---
include/migration/migration.h |2 ++
migration.c
This patch enables us to know RunState transition. We only added a
trace function in runstate_set().
Signed-off-by: Kazuya Saito
---
trace-events |1 +
vl.c |2 +-
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/trace-events b/trace-events
index 1011f27..bf508f0
achieve the purpose. So, we're going to add tracepoints for it.
As a first step, we add tracepoints related in live migration which
got us in trouble before.
Kazuya Saito (2):
add trace_tunstate_set()
create migratestate_set, modify migratestate transition add
trace_migratestat
24 matches
Mail list logo