[PATCH] Generated event stream metadata file

[Ravindra Kumar Meena]

>
>
> > +/* 1024 events are defined. The events are taking values from 0 to
> 1023. */
> > +typedef enum events_e : uint64_t {
> Does this make the enum forced into a 64-bit integer type?
>
Yes, the rtems_record_event variable is 64 bit.

>
> > +} rtems_record_event;
> > +
> > +trace {
> > +    major = 1;
> > +    minor = 8;
> > +    byte_order = le;
> The byte order may depend on the architecture of the CPU that
> generates the trace, right?
>
Yes. It can depend on architecture as well.

>
> > +};
> > +
> > +stream {
> > +    event.header := struct {
> > +        uint32_t id;
> > +    };
> > +};
> > +
> > +event {
> > +    name = "RTEMS_RECORDING_EVENT";
> > +    id=0;
> > +    fields := struct {
> > +               timestamp_t                  ns;
> > +               uint32_t                     cpu;
> > +        rtems_record_event           events;
> Is the rtems_record_event in a stream 64-bits?
>
Yes.

I am really stuck here. I am trying every possible way but only one
variable is printing the wrong value in babeltrace.


-- 
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190625/03df3af4/attachment.html>