On 18/07/2019 07:38, Ravindra Kumar Meena wrote:
Hi,I am facing difficulty in adding event.header in client-side. struct event_header_compact { enum : uint5_t { compact = 0 ... 30, extended = 31 } id; variant <id> { struct { uint27_clock_monotonic_t timestamp; } compact; struct { uint32_t id; uint64_clock_monotonic_t timestamp; } extended; } v; } align(8); This is what I have tried. https://github.com/rmeena840/rtems-tools/commit/b2ffc3d5b5ffd97075f1ed9028bcb8098e241e2b Have a look. Please don't build it it's not working yet.
I would use two structures for this in C, one for the compact header and one for the large header. I would not use bit fields in C.
You have to figure out how the 27-bit timestamp works. It must relative to some reference point.
How is the id used? We are interested in the sched_switch events. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
