On 16.12.21 г. 14:36 ч., Steven Rostedt wrote:
On Thu, 16 Dec 2021 14:29:00 +0200 Yordan Karadzhov <y.karadz@xxxxxxxxx> 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
|