Hi all, On 16.12.21 г. 9:11 ч., Jan Kiszka wrote:
On 16.12.21 04:03, Steven Rostedt wrote:On Wed, 15 Dec 2021 21:16:48 -0500 Hongzhan Chen <hongzhan.chen@xxxxxxxxx> 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 :-)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. Cheers, Yordan
Thanks, Jan
|