linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Hongzhan Chen <hongzhan.chen@intel.com>
Cc: linux-trace-devel@vger.kernel.org, jan.kiszka@siemens.com,
	Yordan Karadzhov <y.karadz@gmail.com>
Subject: Re: [RFC PATCH 0/1] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch.
Date: Wed, 15 Dec 2021 22:03:27 -0500	[thread overview]
Message-ID: <20211215220327.0daae29e@gandalf.local.home> (raw)
In-Reply-To: <20211216021649.7273-1-hongzhan.chen@intel.com>

On Wed, 15 Dec 2021 21:16:48 -0500
Hongzhan Chen <hongzhan.chen@intel.com> wrote:

> I do not know if this patch can be accepted in upstream from function's
> view because it is xenomai related which still be different from
> pure kernel-shark for pure linux. But it is still independent plugin
> which would not influence other kernel-shark's functions and the plugin
> would not take effect if there is no cobalt_switch_context event found
> in trace data.

We are perfectly happy to accept plugins for various OSs, not just pure
Linux :-)

Welcome to the KernelShark Community.

Note, Yordan is now the maintainer of KernelShark so I'll let him review
the patches.

Thanks!

-- Steve

  parent reply	other threads:[~2021-12-16  3:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16  2:16 [RFC PATCH 0/1] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch Hongzhan Chen
2021-12-16  2:16 ` [RFC PATCH 1/1] " Hongzhan Chen
2021-12-16 12:36   ` Yordan Karadzhov
2021-12-17  2:45     ` Chen, Hongzhan
2021-12-16  3:03 ` Steven Rostedt [this message]
2021-12-16  7:11   ` [RFC PATCH 0/1] " Jan Kiszka
2021-12-16 12:29     ` Yordan Karadzhov
2021-12-16 12:36       ` Steven Rostedt
2021-12-16 12:43         ` Yordan Karadzhov

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=20211215220327.0daae29e@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=hongzhan.chen@intel.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --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).