linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yordan Karadzhov <y.karadz@gmail.com>
To: Hongzhan Chen <hongzhan.chen@intel.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] kernel-shark: Add instroduction of external Xenomai plugin
Date: Wed, 13 Apr 2022 15:47:13 +0300	[thread overview]
Message-ID: <54a182cf-3452-ea7a-7f9f-947a877b9212@gmail.com> (raw)
In-Reply-To: <20220411020339.363-1-hongzhan.chen@intel.com>

Applied.

Thanks Hongzhan!
Yordan

On 11.04.22 г. 5:03 ч., Hongzhan Chen wrote:
> introduce external Xenomai plugin in README as a reference to
> implement and build stand-alone plugin.
> 
> Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
> 
> diff --git a/README b/README
> index 37ccd95..d3bceaa 100644
> --- a/README
> +++ b/README
> @@ -114,6 +114,14 @@ CMake examples:
>   
>       cmake -DCMAKE_BUILD_TYPE=Package -DCMAKE_C_FLAGS_PACKAGE="-O3 -pedantic"  ../
>   
> +External plugin example:
> +------------------------------------------------------------
> +    KernelShark also supports stand-alone plugin except for build-in. There is
> +    a real example under https://source.denx.de/Xenomai/xenomai/-/tree/next/tracing/kernelshark/,
> +    which is to visualize out-of-band state of realtime task with hollow cobalt
> +    blue box mainly when there is cobalt context switches in Xenomai. As its
> +    implemention mainly refers to build-in plugin-sched_events, it shares common
> +    plugin features such as clickable shapes.
>   
>   Contributions:
>   ------------------------------------------------------------

      reply	other threads:[~2022-04-13 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  2:03 [PATCH] kernel-shark: Add instroduction of external Xenomai plugin Hongzhan Chen
2022-04-13 12:47 ` Yordan Karadzhov [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=54a182cf-3452-ea7a-7f9f-947a877b9212@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=hongzhan.chen@intel.com \
    --cc=linux-trace-devel@vger.kernel.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).