1. 22 Jul, 2021 1 commit
  2. 04 Jun, 2021 1 commit
  3. 12 May, 2021 1 commit
  4. 05 May, 2021 2 commits
  5. 02 Dec, 2019 2 commits
  6. 03 Jun, 2019 1 commit
    • Jan Kiszka's avatar
      cobalt/kernel: Simplify mayday processing · 4e7bb325
      Jan Kiszka authored
      
      
      The mayday mechanism exists in order to kick a xenomai userspace task
      into secondary mode while it is running userspace code. For that, we ask
      I-pipe to call us back when the task was interrupted and is about to
      return to userspace.
      
      So far we defer the relaxation from that callback via a VDSO-like
      mechanism that triggers a special syscall to the return path of that
      very same syscall. However, that is not desirable because it is a
      complex, arch-specific mechanism that can easily break and,
      specifically, that destroys the backtrace of ptraced tasks.
      
      Fortunately, we can fulfill the needs of mayday also by relaxing
      the task directly from the mayday callback. Tested successfully on
      x86-64 and ARM.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      4e7bb325
  7. 19 Mar, 2019 1 commit
  8. 03 Jul, 2018 8 commits
  9. 01 Jul, 2017 1 commit
  10. 09 May, 2017 1 commit
  11. 14 May, 2016 1 commit
  12. 27 Nov, 2015 1 commit
  13. 10 Nov, 2015 1 commit
  14. 30 Sep, 2015 2 commits
  15. 18 Jun, 2015 1 commit
  16. 17 Oct, 2014 1 commit
  17. 21 Sep, 2014 1 commit
  18. 09 Sep, 2014 2 commits
  19. 03 Sep, 2014 1 commit
    • Philippe Gerum's avatar
      cobalt: make core handle type 32/64bit-neutral · b5ecfc98
      Philippe Gerum authored
      There is no point in using 64bit long Cobalt handles internally on
      64bit platforms. However it makes sense to keep them as 32bit values
      so that we may use them as atomic operands on either sides of a
      64bit(kernel) <-> 32bit(user) ABI.
      
      At this chance, boilerplate/atomic.h is sanitized for disambiguating
      regular and long atomic set/get operations.
      b5ecfc98
  20. 21 Aug, 2014 1 commit
  21. 03 Jul, 2014 1 commit
  22. 01 Jul, 2014 1 commit
    • Philippe Gerum's avatar
      cobalt: fix naming consistency issues with *_np() calls · 50bd5540
      Philippe Gerum authored
      To match the GNU extension equivalent, pthread_set_name_np() is
      renamed to pthread_setname_np(). For consistency with the previous
      change, pthread_set_mode_np() becomes pthread_setmode_np().
      
      The former calls will be available from the upcoming transition kit.
      50bd5540
  23. 17 Jun, 2014 1 commit
    • Philippe Gerum's avatar
      cobalt/posix: drop pthread_make_periodic_np/wait_period_np services · bf112060
      Philippe Gerum authored
      We have no more in-tree users of these calls.
      
      With the introduction of services to support real-time signals, those
      two non-portable calls have become redundant. Instead, Cobalt-based
      applications should set up a periodic timer using the
      timer_create()+timer_settime() call pair, then wait for release points
      via sigwaitinfo(). Overruns can be detected by looking at the
      siginfo.si_overrun field.
      
      Alternatively, applications may obtain a file descriptor referring to
      a Cobalt timer via the timerfd() call, and read() from it to wait for
      timeouts.
      
      In addition, applications may include a timer in a synchronous
      multiplexing operation involving other event sources, by passing a
      file descriptor returned by the timerfd() service to a select() call.
      bf112060
  24. 02 Jun, 2014 1 commit
  25. 27 May, 2014 2 commits
  26. 19 May, 2014 1 commit
  27. 13 May, 2014 1 commit
  28. 12 May, 2014 1 commit