From: Yordan Karadzhov <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Hongzhan Chen <hongzhan.chen@intel.com>,
linux-trace-devel@vger.kernel.org,
Dario Faggioli <dfaggioli@suse.com>,
giuseppe.eletto@edu.unito.it
Subject: Re: [RFC PATCH 0/1] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch.
Date: Thu, 16 Dec 2021 14:43:51 +0200 [thread overview]
Message-ID: <cb81f51d-14d8-c5db-5181-767574fa9cb1@gmail.com> (raw)
In-Reply-To: <20211216073626.41d6791e@gandalf.local.home>
On 16.12.21 г. 14:36 ч., Steven Rostedt wrote:
> On Thu, 16 Dec 2021 14:29:00 +0200
> Yordan Karadzhov <y.karadz@gmail.com> wrote:
>
>>> We were just wondering how to handle potential (we have no concrete case
>>> so far) variations of trace points along releases of those "various OSs"
>>> best and were therefore also considering maintaining the plugin in
>>> lock-step with the Xenomai releases. How does KernelShark manage such cases?
>>>
>>
>> I am adding Dario and Giuseppe to the loop, because they may de interested in this work.
>>
>> We can take the plugin upstream as long as it does not add any xenomai specific dependencies (headers or libraries).
>> In such case you have to guarantee a persistent commitment for co-maintaining it.
>> Alternatively, you can maintain the plugin in a stand alone repository. Dario and Giuseppe are doing this.
>
> I believe Jan is asking about this stand alone like scenario. Where the
> plugin is actually maintained in the Xenomai repository.
>
> Is there a way to have the KernelShark user config file automatically load a
> plugin? That way a user could have the plugins they are interested in (that
> are not part of the main repository) automatically loaded every time they
> start KernelShark?
Currently not, but this can be implemented.
Y.
>
> -- Steve
>
prev parent reply other threads:[~2021-12-16 12:43 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 ` [RFC PATCH 0/1] " Steven Rostedt
2021-12-16 7:11 ` Jan Kiszka
2021-12-16 12:29 ` Yordan Karadzhov
2021-12-16 12:36 ` Steven Rostedt
2021-12-16 12:43 ` 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=cb81f51d-14d8-c5db-5181-767574fa9cb1@gmail.com \
--to=y.karadz@gmail.com \
--cc=dfaggioli@suse.com \
--cc=giuseppe.eletto@edu.unito.it \
--cc=hongzhan.chen@intel.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).