linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
	Stefano De Venuto <stefano.devenuto99@gmail.com>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [RFC] Open multiple trace files and, if possible, pair them
Date: Thu, 11 Mar 2021 19:32:53 +0100	[thread overview]
Message-ID: <09e8114cebcd10d171bd8b0557dbf69ef61b7298.camel@suse.com> (raw)
In-Reply-To: <20210311125040.25339858@gandalf.local.home>

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

On Thu, 2021-03-11 at 12:50 -0500, Steven Rostedt wrote:
> On Thu, 11 Mar 2021 18:37:03 +0100
> Dario Faggioli <dfaggioli@suse.com> wrote:
> > 
> > So, what would be the way forward here. I'm guessing re-doing the
> > patch
> > on top of the new API?
> 
> With the new API it may not be necessary.
> 
Right.

> As we are making it where the guest files will show the same output
> regardless of being paired or not by default. That is, we are going
> to
> store the synchronization information in each trace.dat file (for the
> host
> and all the guests), and the trace.dat files will display the same
> time
> stamp regardless of if it is being displayed with other trace.dat
> files or
> stand alone.
> 
Yep, saw it.

In fact, my mistake was to think that opening multiple trace files
would still need some work. But, as a matter of fact, that also works
already, right?

In which case, we will "just" apply the patches with the new API and
continue our work on top of them.

And sorry for the noise. :-)

Regards
-- 
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-03-11 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  6:28 [RFC] Open multiple trace files and, if possible, pair them Stefano De Venuto
2021-03-05  9:18 ` raistlin.df
2021-03-05 14:47   ` Steven Rostedt
2021-03-05 13:50 ` Tzvetomir Stoyanov
2021-03-11 17:37   ` Dario Faggioli
2021-03-11 17:50     ` Steven Rostedt
2021-03-11 17:53       ` Steven Rostedt
2021-03-11 18:32       ` Dario Faggioli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09e8114cebcd10d171bd8b0557dbf69ef61b7298.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stefano.devenuto99@gmail.com \
    --cc=tz.stoyanov@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).