GitLab

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

With recent glibc (at least 2.34), autoconf fails to detect
pthread_mutexattr_setrobust_np. But that is long deprecated anyway. So
switch to pthread_mutexattr_setrobust and only fall back to _np when
needed.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Recent glibc (at leasst 2.34) triggers

  CC       libposix_fork_a-posix-fork.o
In file included from posix-fork.c:11:
../../../include/boilerplate/libc.h:248:10: error: expected identifier or '(' before '{' token
  248 |         ({ ENOSYS; })
      |          ^

So switch to a static inline, like for all the other stubs.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Was found by latest gcc-11 and -Werror=mismatched-dealloc.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

glibx 2.34 and newer annotated pthread_setspecific in a way that gcc-11
complains about non-NULL pointers that are outside of what is considered
valid. So use dummy addresses instead. namely the related pthread keys.
Those pointers will never be dereferenced in both use cases.

See also https://sourceware.org/bugzilla/show_bug.cgi?id=28458

.
Reported-by: Vitaly Chikunov <vt@altlinux.org>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Needed for recent kernels.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Was a nop and got removed in kernel 5.12.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Kernel 5.14 requires this.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Identical to MAX_USER_RT_PRIO which was removed in 5.12.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Enforced by recent kernels.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Required with kernel 5.15 to avoid duplicate includes. Provide a stub
for older kernels that continues to use the toolchain header.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Wrap it on __close_fd for older kernels.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

And wrap the previous open-coded initialization for older kernels.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

abs_timeout is not provided in ticks but actually seconds/nanoseconds.
Clarify this and remove the related wrong note from those functions
headers.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Validates all three rt_pipe_read functions /wrt non-blocking read as
well as timeouts.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

A missing initialization led to early termination and crashes.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

The underlying IPC driver takes relative timeouts, but
rt_pipe_read_timed so far submitted absolute ones. This fixes this
function and also adds a non-inline rt_pipe_read to avoid pointless
conversions from relative to absolute and then to relative again.
Reported-by: Mauro S. <mau.salvi@tin.it>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This brings us below default CONFIG_FRAME_WARN with CONFIG_MAXSMP=y on
x86, avoiding the related compile-time warning.
Reported-by: Florian Bezdeka <florian.bezdeka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Analogously to dfb55d64

.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This left timers and possibly other resources registers while freeing
the object. The resulting crash was easily triggerable by creating
threads until the registry was full.
Reported-by: Henning Schild <henning.schild@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

The introduction of dovetail support with the change in the realtime
clock semantics and related interface changes (vDSO usage) is an ABI
change that needs a revision bump.

Strictly spoken, PowerPC is only theoretically affected as it lacks
dovetail support, but it's simpler to bump than to safely exclude all
possibly side effects even on this arch.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Extending the test suite for recvmmsg64 test.
Signed-off-by: Song Chen <chensong_2000@189.cn>
[Florian: Rebased the patch on top of next]
[Florian: switched to CLOCK_MONOTONIC]
[Florian: Fixed error handling of the socket() call]
Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

If libc reports time64_t support, recvmmsg is dispatched to the
time64_t based syscall.
Signed-off-by: Song Chen <chensong_2000@189.cn>
Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Add a syscall specific for recvmmsg64 with 64bit time_t.
Signed-off-by: Song Chen <chensong_2000@189.cn>
[Florian: Fixed some style issues]
[Florian: Added Song's Signed-off back (malformed patch received)]
[Florian: Fixed tracing infrastructure]
Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
[Jan: reordered include statement]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This caused troubles with modern gcc that starts to use those regs for
other purposes. Seen with gcc-10 on Debian 11 e.g.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This was missed in c4c2fc21

.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Provide choices to switch clock between MONO and REALTIME for getting
different timestamp since gpio driver already provide choosable service.
Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

When test is interrupted, avg latency need to be calcuated once
to avoid large latency showing even though it may not be quite
accurate.
Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
[Jan: tuning of wording and output format]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Ensures build-testing. We need to enable a couple of dependencies of the
driver for that.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This ensures that Xenomai GPIO drivers are built. It's a dependency of
XENO_DRIVERS_GPIO that is not automatically enabled.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Add support for Intel Cherryview pin controller driver
Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
[Jan: renamed 'compat_array' to 'label_array', folded in right removal function]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

To find gpiochip for non-OF platforms like x86
Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
[Jan: adjust parameter name 'compat' to 'label', reindent]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Rename interface name because it is independent of OF platform and
non-OF platform would also call it to remove rtdm gpio chip device.
Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
[Jan: choose conflict-free rtdm_gpiochip_remove_by_type as name]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This is in line with other drivers and should avoid surprises like [1]
in the future.

[1] https://xenomai.org/pipermail/xenomai/2021-June/045661.html

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

The API's default will change, so select monotonic explicitly.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This allows to compare timestamps of GPIO pins against other devices and
ensures that the stamps are synchronized cross-systems in case PTP is in
use (dovetail-based kernels). Keep default to monotonic for now.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Especially 4.19 is not 2038 safe and 32 bit kernels do not have
CONFIG_64BIT_TIME set, which ends up in __kernel_timespec being defined
in a non y2038 safe way.

cobalt_get_timespec64 will copy the upper bytes of the sec field into
the nsec field, which is always zero.

Testing y2038 syscalls on a non y2038 safe kernel doesn't make sense,
hence limiting the test runs to kernels with 2038 support.
Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Make sure that named semaphores as well as mqueues are exported to the
procfs.
Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
[Jan: delay procfs_exists to account for asynchronous /proc update]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>