On 01.03.22 09:21, Chen, Hongzhan wrote: > >> >> -----Original Message----- >> From: Jan Kiszka <[email protected]> >> Sent: Tuesday, March 1, 2022 3:41 PM >> To: Chen, Hongzhan <[email protected]>; [email protected] >> Subject: Re: [PATCH 4/4] libtraceevent: Add Add xenomai_schedparams plugin >> for libtraceevent >> >> On 28.02.22 06:40, Hongzhan Chen wrote: >>> For cobalt thread, there is special struct param_ex data stored in >>> data record, we need to parse and print its content out correctly >>> to hint user when using libtraceevent. >>> >> >> While libtraceevent can be used along with KernelShark, it's not bound >> to it. You can also perfectly use it with pure command line tooling >> (trace-cmd). That would make it interesting for your UI-free demo images >> (xenomai-images). So I would recommand controlling its build >> independently of KernelShark. >> >>> Signed-off-by: Hongzhan Chen <[email protected]> >>> --- >>> configure.ac | 1 + >>> kernel-shark/Makefile.am | 6 +- >> >> Maybe call the top-level directory "tracing" instead. > > It was supposed that the building of all plugins is controlled by one option > --with-kernelshark in my case. As you suggested ,does that means we need to > add one more option like --with-libtraceevent to build libtraceevent > standalone independent from building kernelshark plugin. Or we replace > --with-kernelshark with- -with-tracing to build all plugins under tracing > folder with sole option? >
Yes, --with-libtraceevent, and then maybe make --with-kernelshark imply the former if it depends on it technically. Jan -- Siemens AG, Technology Competence Center Embedded Linux
