(2013/06/11 15:50), Gleb Natapov wrote:
On Mon, Jun 10, 2013 at 05:28:23PM -0300, Marcelo Tosatti wrote:
On Mon, Jun 10, 2013 at 07:38:34PM +0300, Gleb Natapov wrote:
Guest traces contain vcpu number and not pid (because guest is unaware
of host PID).
No, guest trace is just a regular ftrace
On Mon, Jun 10, 2013 at 05:28:23PM -0300, Marcelo Tosatti wrote:
> On Mon, Jun 10, 2013 at 07:38:34PM +0300, Gleb Natapov wrote:
> > > Guest traces contain vcpu number and not pid (because guest is unaware
> > > of host PID).
> > >
> > No, guest trace is just a regular ftrace done inside a guest.
On Mon, Jun 10, 2013 at 07:38:34PM +0300, Gleb Natapov wrote:
> > Guest traces contain vcpu number and not pid (because guest is unaware
> > of host PID).
> >
> No, guest trace is just a regular ftrace done inside a guest. It contains
> guest's PIDs which is useless for host.
# tracer: nop
#
# e
On Mon, Jun 10, 2013 at 11:04:24AM -0300, Marcelo Tosatti wrote:
> On Mon, Jun 10, 2013 at 01:05:05PM +0300, Gleb Natapov wrote:
> > On Mon, Jun 10, 2013 at 06:30:42PM +0900, Yoshihiro YUNOMAE wrote:
> > > Hi Gleb,
> > >
> > > (2013/06/09 20:14), Gleb Natapov wrote:
> > > >On Fri, Jun 07, 2013 at
On Mon, Jun 10, 2013 at 01:05:05PM +0300, Gleb Natapov wrote:
> On Mon, Jun 10, 2013 at 06:30:42PM +0900, Yoshihiro YUNOMAE wrote:
> > Hi Gleb,
> >
> > (2013/06/09 20:14), Gleb Natapov wrote:
> > >On Fri, Jun 07, 2013 at 02:22:22PM +0900, Yoshihiro YUNOMAE wrote:
> > >>(2013/06/06 20:33), Gleb Nat
Hi Gleb,
(2013/06/10 19:05), Gleb Natapov wrote:
On Mon, Jun 10, 2013 at 06:30:42PM +0900, Yoshihiro YUNOMAE wrote:
Hi Gleb,
(2013/06/09 20:14), Gleb Natapov wrote:
On Fri, Jun 07, 2013 at 02:22:22PM +0900, Yoshihiro YUNOMAE wrote:
(2013/06/06 20:33), Gleb Natapov wrote:
On Wed, Jun 05, 201
On Mon, Jun 10, 2013 at 06:30:42PM +0900, Yoshihiro YUNOMAE wrote:
> Hi Gleb,
>
> (2013/06/09 20:14), Gleb Natapov wrote:
> >On Fri, Jun 07, 2013 at 02:22:22PM +0900, Yoshihiro YUNOMAE wrote:
> >>(2013/06/06 20:33), Gleb Natapov wrote:
> >>>On Wed, Jun 05, 2013 at 09:23:22PM -0300, Marcelo Tosatti
Hi Gleb,
(2013/06/09 20:14), Gleb Natapov wrote:
On Fri, Jun 07, 2013 at 02:22:22PM +0900, Yoshihiro YUNOMAE wrote:
(2013/06/06 20:33), Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 09:23:22PM -0300, Marcelo Tosatti wrote:
On Tue, Jun 04, 2013 at 05:36:19PM +0900, Yoshihiro YUNOMAE wrote:
Add
On Fri, Jun 07, 2013 at 02:22:22PM +0900, Yoshihiro YUNOMAE wrote:
> (2013/06/06 20:33), Gleb Natapov wrote:
> >On Wed, Jun 05, 2013 at 09:23:22PM -0300, Marcelo Tosatti wrote:
> >>On Tue, Jun 04, 2013 at 05:36:19PM +0900, Yoshihiro YUNOMAE wrote:
> >>>Add a tracepoint write_tsc_offset for tracing
On Fri, Jun 07, 2013 at 02:22:22PM +0900, Yoshihiro YUNOMAE wrote:
> (2013/06/06 20:33), Gleb Natapov wrote:
> >On Wed, Jun 05, 2013 at 09:23:22PM -0300, Marcelo Tosatti wrote:
> >>On Tue, Jun 04, 2013 at 05:36:19PM +0900, Yoshihiro YUNOMAE wrote:
> >>>Add a tracepoint write_tsc_offset for tracing
On Thu, Jun 06, 2013 at 02:33:06PM +0300, Gleb Natapov wrote:
> On Wed, Jun 05, 2013 at 09:23:22PM -0300, Marcelo Tosatti wrote:
> > On Tue, Jun 04, 2013 at 05:36:19PM +0900, Yoshihiro YUNOMAE wrote:
> > > Add a tracepoint write_tsc_offset for tracing TSC offset change.
> > > We want to merge ftrac
(2013/06/06 20:33), Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 09:23:22PM -0300, Marcelo Tosatti wrote:
On Tue, Jun 04, 2013 at 05:36:19PM +0900, Yoshihiro YUNOMAE wrote:
Add a tracepoint write_tsc_offset for tracing TSC offset change.
We want to merge ftrace's trace data of guest OSs and the
On Wed, Jun 05, 2013 at 09:23:22PM -0300, Marcelo Tosatti wrote:
> On Tue, Jun 04, 2013 at 05:36:19PM +0900, Yoshihiro YUNOMAE wrote:
> > Add a tracepoint write_tsc_offset for tracing TSC offset change.
> > We want to merge ftrace's trace data of guest OSs and the host OS using
> > TSC for timestam
On Tue, Jun 04, 2013 at 05:36:19PM +0900, Yoshihiro YUNOMAE wrote:
> Add a tracepoint write_tsc_offset for tracing TSC offset change.
> We want to merge ftrace's trace data of guest OSs and the host OS using
> TSC for timestamp in chronological order. We need "TSC offset" values for
> each guest wh
Add a tracepoint write_tsc_offset for tracing TSC offset change.
We want to merge ftrace's trace data of guest OSs and the host OS using
TSC for timestamp in chronological order. We need "TSC offset" values for
each guest when merge those because the TSC value on a guest is always the
host TSC plus
15 matches
Mail list logo