Thank you Genevieve, "cpu" field works.
Yonghong
On Mon, Jan 21, 2019 at 7:57 PM Genevieve Bastien
wrote:
> Hi Yonghong,
>
> With TraceCompass XML analyses, you can use as state value or attribute an
> eventField called 'cpu' to get the CPU id of an event. For example,
>
>
>
> With LTTng trac
Hi Yonghong,
With TraceCompass XML analyses, you can use as state value or attribute
an eventField called 'cpu' to get the CPU id of an event. For example,
With LTTng traces, it will automatically be the CPU, obtained as Mathieu
described, no need for an extra field.
Regards,
Geneviève
On 2
Thank you. make sense. I am using Trace Compass XML based approach to
display UST trace records. Using CPU id helps me easier to sort out the
event records in trace compass. I will check out more on trace compass.
Yonghong
On Mon, Jan 21, 2019 at 2:06 PM Mathieu Desnoyers <
mathieu.desnoy...@eff
- On Jan 21, 2019, at 12:14 PM, Yonghong Yan wrote:
> I saw there is cpu_id field in babeltrace list, how can I add it to the
> context
> of UST tracepoint events. lttng add-context --list does not show that field
> and
> I do not see a similar field for the cpu_id.
The cpu_id context onl
