RTEMS | Draft: cpukit: Create DHRL Library for DRAM Latency Mitigation (!1193)

[Wayne Thornton (@wmthornton-dev)]

Wayne Thornton started a new discussion on cpukit/dhrl/dhrl.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_148403

 > +      RTEMS_WAIT | RTEMS_EVENT_ALL,
 > +      RTEMS_NO_TIMEOUT,
 > +      &events
 > +    );
 > +
 > +    // SMP SAFETY: Guarantee we see the pointers set by the main core
 > +    atomic_thread_fence( memory_order_acquire );
 > +
 > +    // Capture the active epoch for this specific race
 > +    unsigned int my_epoch = atomic_load_explicit(
 > +      &dhrl_active_epoch,
 > +      memory_order_acquire
 > +    );
 > +
 > +    // Grab the specific target address for this channel
 > +    volatile void *target_addr = ( channel_id == 0 ) ? dhrl_target_addr_a

@joel semantically, I chose to use ternary operators here as opposed to a standard if-else statement. As it stands, this operates the same way but I'm just seeking clarification if there is a preference in the RTEMS source for either/or?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1193#note_148403
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260410/3ebb694d/attachment-0001.htm>