(2013/08/27 22:00), Steven Rostedt wrote:
On Tue, 27 Aug 2013 17:07:34 +0900
Yoshihiro YUNOMAE wrote:
et, but I'd like to
add such feature to fix host/guest clock difference in the next series.
TSC offset values can be gotten as write_tsc_offset trace event from
kernel-3.11. (see
(2013/08/27 22:00), Steven Rostedt wrote:
On Tue, 27 Aug 2013 17:07:34 +0900
Yoshihiro YUNOMAE yoshihiro.yunomae...@hitachi.com wrote:
et, but I'd like to
add such feature to fix host/guest clock difference in the next series.
TSC offset values can be gotten as write_tsc_offset trace event from
On Tue, 27 Aug 2013 17:07:34 +0900
Yoshihiro YUNOMAE wrote:
et, but I'd like to
> add such feature to fix host/guest clock difference in the next series.
> TSC offset values can be gotten as write_tsc_offset trace event from
> kernel-3.11. (see https://lkml.org/lkml/2013/6/12/72)
> How do you
Hi Steven,
(2013/08/26 23:22), Steven Rostedt wrote:
On Mon, 26 Aug 2013 10:46:38 +0900
Yoshihiro YUNOMAE wrote:
The --date option is used because the two machines are not in sync with
the trace time stamp. What the date option does, is to sync the
timestamp up with the gettimeofday and the
Hi Steven,
(2013/08/26 23:22), Steven Rostedt wrote:
On Mon, 26 Aug 2013 10:46:38 +0900
Yoshihiro YUNOMAE yoshihiro.yunomae...@hitachi.com wrote:
The --date option is used because the two machines are not in sync with
the trace time stamp. What the date option does, is to sync the
timestamp
On Tue, 27 Aug 2013 17:07:34 +0900
Yoshihiro YUNOMAE yoshihiro.yunomae...@hitachi.com wrote:
et, but I'd like to
add such feature to fix host/guest clock difference in the next series.
TSC offset values can be gotten as write_tsc_offset trace event from
kernel-3.11. (see
On Mon, 26 Aug 2013 10:46:38 +0900
Yoshihiro YUNOMAE wrote:
> > The --date option is used because the two machines are not in sync with
> > the trace time stamp. What the date option does, is to sync the
> > timestamp up with the gettimeofday and the output reports that. This
> > allows the two
On Mon, 26 Aug 2013 10:46:38 +0900
Yoshihiro YUNOMAE yoshihiro.yunomae...@hitachi.com wrote:
The --date option is used because the two machines are not in sync with
the trace time stamp. What the date option does, is to sync the
timestamp up with the gettimeofday and the output reports
Hi Steven,
Thank you for reviewing my patches.
Sorry for the late reply.
(2013/08/21 1:00), Steven Rostedt wrote:
On Mon, 19 Aug 2013 18:46:20 +0900
Yoshihiro YUNOMAE wrote:
d) merge feature of trace data of multiple guests and a host in chronological
order
Current trace-cmd cannot
Hi Steven,
Thank you for reviewing my patches.
Sorry for the late reply.
(2013/08/21 1:00), Steven Rostedt wrote:
On Mon, 19 Aug 2013 18:46:20 +0900
Yoshihiro YUNOMAE yoshihiro.yunomae...@hitachi.com wrote:
d) merge feature of trace data of multiple guests and a host in chronological
On Mon, 19 Aug 2013 18:46:20 +0900
Yoshihiro YUNOMAE wrote:
> d) merge feature of trace data of multiple guests and a host in chronological
>order
> Current trace-cmd cannot merge trace data of multiple guests and a host in
> chronological order. If an user wants to analyze an I/O delay
On Mon, 19 Aug 2013 18:46:20 +0900
Yoshihiro YUNOMAE yoshihiro.yunomae...@hitachi.com wrote:
d) merge feature of trace data of multiple guests and a host in chronological
order
Current trace-cmd cannot merge trace data of multiple guests and a host in
chronological order. If an user
12 matches
Mail list logo
