[EMAIL PROTECTED] wrote:
Avi Kivity wrote:
Jan Kiszka wrote:
Avi Kivity wrote:
Liu, Eric E wrote:
Since we already have had debugfs_entries and some other kernel
debug mechanism to use, does this kvmtrace make sense? Any
comment is welcomed.
This looks very useful. While kvm_stat
Liu, Eric E wrote:
Hi,
The following patches port xentrace to kvm which is useful for
performance tuning and debugging.
It is designed to allow debugging traces of kvm to be generated on
Up/Smp machines. Each trace entry is outputted in a trace ring buffer
for per cpu which is mapped to
Avi Kivity wrote:
Liu, Eric E wrote:
Hi,
The following patches port xentrace to kvm which is useful for
performance tuning and debugging.
It is designed to allow debugging traces of kvm to be generated on
Up/Smp machines. Each trace entry is outputted in a trace ring buffer
for per cpu
Jan Kiszka wrote:
Avi Kivity wrote:
Liu, Eric E wrote:
Hi,
The following patches port xentrace to kvm which is useful for
performance tuning and debugging.
It is designed to allow debugging traces of kvm to be generated on
Up/Smp machines. Each trace entry is outputted in a trace
Avi Kivity wrote:
Jan Kiszka wrote:
Avi Kivity wrote:
Liu, Eric E wrote:
Hi,
The following patches port xentrace to kvm which is useful for
performance tuning and debugging.
It is designed to allow debugging traces of kvm to be generated on
Up/Smp machines. Each trace entry is
Hi,
The following patches port xentrace to kvm which is useful for
performance tuning and debugging.
It is designed to allow debugging traces of kvm to be generated on
Up/Smp machines. Each trace entry is outputted in a trace ring buffer
for per cpu which is mapped to userspace, and the userspace
