From: Steven Rostedt <rostedt@goodmis.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Dario Faggioli <dfaggioli@suse.com>,
Giuseppe Eletto <giuseppe.eletto@edu.unito.it>,
<linux-trace-devel@vger.kernel.org>,
<xen-devel@lists.xenproject.org>,
Enrico Bini <enrico.bini@unito.it>
Subject: Re: A KernelShark plugin for Xen traces analysis
Date: Wed, 14 Apr 2021 15:07:52 -0400 [thread overview]
Message-ID: <20210414150752.34366b99@gandalf.local.home> (raw)
In-Reply-To: <7184a7d7-6bca-4106-d70e-8cf9d5b227fb@citrix.com>
On Wed, 14 Apr 2021 19:11:19 +0100
Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> Where the plugin (ought to) live depends heavily on whether we consider
> the trace format a stable ABI or not.
Agreed. Like the VMware plugin to handle ESX traces. It's internal and not
published as the API is not stable.
But if it ever becomes stable, and you would like it to live with
KernelShark, we are looking to have a place to store third party plugins.
We are working to make sure that the API for KernelShark plugins remains
stable, so your plugins should always work too.
-- Steve
next prev parent reply other threads:[~2021-04-14 19:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 14:28 A KernelShark plugin for Xen traces analysis Giuseppe Eletto
2021-04-13 15:33 ` Andrew Cooper
2021-04-14 17:31 ` Dario Faggioli
2021-04-14 18:11 ` Andrew Cooper
2021-04-14 19:07 ` Steven Rostedt [this message]
2021-04-15 0:50 ` A KernelShark plugin for Xen traces analysis Dario Faggioli
2021-04-15 13:29 ` Steven Rostedt
2021-04-14 21:51 ` A KernelShark plugin for Xen traces analysis Dario Faggioli
2021-04-13 15:46 ` A KernelShark plugin for Xen traces analysis Steven Rostedt
2021-04-14 10:07 ` Andrew Cooper
2021-04-14 13:43 ` Steven Rostedt
2021-04-14 20:05 ` Andrew Cooper
2021-04-15 0:41 ` Dario Faggioli
2021-04-15 0:13 ` Dario Faggioli
2021-04-14 22:11 ` Dario Faggioli
2021-04-14 22:25 ` Steven Rostedt
2021-04-14 9:25 ` A KernelShark plugin for Xen traces analysis Yordan Karadzhov (VMware)
2021-04-14 17:46 ` Dario Faggioli
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=20210414150752.34366b99@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=andrew.cooper3@citrix.com \
--cc=dfaggioli@suse.com \
--cc=enrico.bini@unito.it \
--cc=giuseppe.eletto@edu.unito.it \
--cc=linux-trace-devel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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).