From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Cc: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] kernel-shark-2.alpha: Use new tracecmd API to open guest tracing file
Date: Fri, 3 Apr 2020 09:25:55 -0400 [thread overview]
Message-ID: <20200403092555.7a787af5@gandalf.local.home> (raw)
In-Reply-To: <CAPpZLN7NLm=r3y76M1oZAVRh5S7FOCk6-ieSKOzZVtMOCJ=uxQ@mail.gmail.com>
On Fri, 3 Apr 2020 15:26:49 +0300
Tzvetomir Stoyanov <tz.stoyanov@gmail.com> wrote:
> >
> > Also do we consider a case when we will need to load more than one
> > "primary" stream?
>
> In the host - guest tracing, there is no use case with more than one
> primary stream,
> but may be there could be other use cases where more than one primary
> stream will
> be needed ?
>
> Is it possible to append more than one secondary files, using the
> current KernelShark 2 ?
> I tried appending two files, specifying "-a" option twice, but only
> the first "-a" file was appended.
We should start thinking about nested VMs. What happens if we have a host,
a guest-host and a guest? That is, the guest is a VM on top of the
guest-host, which is a VM on top of the host.
And there could be a guest on top of that guest as well!
-- Steve
next prev parent reply other threads:[~2020-04-03 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 16:45 [PATCH] kernel-shark-2.alpha: Use new tracecmd API to open guest tracing file Tzvetomir Stoyanov (VMware)
2020-04-03 11:39 ` Yordan Karadzhov (VMware)
2020-04-03 12:26 ` Tzvetomir Stoyanov
2020-04-03 13:25 ` Steven Rostedt [this message]
2020-04-03 15:09 ` Yordan Karadzhov (VMware)
2020-04-03 17:12 ` Tzvetomir Stoyanov
2020-04-06 13:24 ` Yordan Karadzhov (VMware)
2020-04-06 14:33 ` Tzvetomir Stoyanov
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=20200403092555.7a787af5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@gmail.com \
--cc=y.karadz@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).