Logger: Pipe the monotonic_remote_transmit_time through event loop
Populate the field in all the network bridges and pipe it through
all the required spots in the event loop. Update all the tests to match
the update.
As part of this, we realized that our modeling of network delay was
wrong. Wakeups don't always take 50 uS if something else triggers the
wakeup and the message is ready in shared memory. This wasn't being
handled properly.
Change-Id: Idf94c5c6d7c87f4d65868c71b1cceedca7bf3853
Signed-off-by: James Kuszmaul <james.kuszmaul@bluerivertech.com>
diff --git a/aos/events/event_loop_runtime.h b/aos/events/event_loop_runtime.h
index 0505852..afc96e2 100644
--- a/aos/events/event_loop_runtime.h
+++ b/aos/events/event_loop_runtime.h
@@ -25,6 +25,7 @@
int64_t monotonic_remote_time;
int64_t realtime_remote_time;
+ int64_t monotonic_remote_transmit_time;
uint32_t queue_index;
uint32_t remote_queue_index;
@@ -48,6 +49,8 @@
offsetof(RustContext, monotonic_remote_time));
static_assert(offsetof(Context, realtime_remote_time) ==
offsetof(RustContext, realtime_remote_time));
+static_assert(offsetof(Context, monotonic_remote_transmit_time) ==
+ offsetof(RustContext, monotonic_remote_transmit_time));
static_assert(offsetof(Context, queue_index) ==
offsetof(RustContext, queue_index));
static_assert(offsetof(Context, remote_queue_index) ==