On 07.01.22 12:10, Yordan Karadzhov wrote:
> Hi Hongzhan and Jan,
>
> Have you decided something about the way this plugin will be maintained?
>
No decision yet. I'm still waiting for an answer on
https://lore.kernel.org/linux-trace-devel/9ac9a1af-6829-425a-7943-755decf7c273@xxxxxxxxx/
regarding maintenance of different tracepoint revisions. That would be
implicit when keeping the plugin in lock-step with the tracepoints in
the same repo.
But then the question would be how mature the interface lifecycle
management of kernelshark and libs is /wrt external plugins. Those may
need to account for potential changes in those APIs over the time, right?
We will likely pick the path that is least inconvenient.
[...]
>> + eventFieldIntervalPlot(argvCpp,
>> + plugin_ctx->cs_data, checkFieldCS,
>> + plugin_ctx->cs_data, checkEntryPid,
>> + makeLatencyBox<XenomaiSwitchBox>,
>> + {0, 0, 255}, // Blue
>
> Perhaps you can use 'cobalt blue' instead of just blue ;-)
>
Makes sense ;)
Seriously: Is there some caption somewhere that explains the meaning of
colors? If so, how to hook into that?
Thanks,
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
|