GitLab

Gilles Chanteperdrix authored Dec 03, 2017 and Philippe Gerum committed Nov 08, 2019

Expose the clocksource to userland processes via the ARM-specific
user-TSC interface.

Gilles Chanteperdrix authored Dec 03, 2017 and Philippe Gerum committed Nov 08, 2019

Expose the clocksource to userland processes via the ARM-specific
user-TSC interface.

Gilles Chanteperdrix authored Dec 03, 2017 and Philippe Gerum committed Nov 08, 2019

Expose the clocksource to userland processes via the ARM-specific
user-TSC interface.

Jan Kiszka authored Apr 02, 2019 and Philippe Gerum committed Nov 08, 2019

Since 9beae1ea

, we are supposed to pass down flags, not just 0 or 1.
Luckily, 1 happened to be FOLL_WRITE, so we did the right thing by
chance.

Moreover, get_user_pages is deprecated in favor of its locked/unlocked/
fast variants.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Jan Kiszka authored Mar 27, 2019 and Philippe Gerum committed Nov 08, 2019

If evtdev should be NULL, we will crash on get_dev_mode(evtdev) further
down. So this test is never false in absence of sever bugs.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Jan Kiszka authored Mar 27, 2019 and Philippe Gerum committed Nov 08, 2019

A long time ago (probably in 2.6-times), someone converted spaces to
tabs, shuffling the layout around this way, and by forgetting to account
for the multi-domain removal.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Jan Kiszka authored Mar 27, 2019 and Philippe Gerum committed Nov 08, 2019

Since 4.9, we need to declare continued lines via KERN_CONT.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

See https://www.xenomai.org/pipermail/xenomai/2019-March/040460.html

Jan Kiszka authored Feb 25, 2019 and Philippe Gerum committed Nov 08, 2019

When a CPU is unplugged, make sure to drop all per-CPU ipipe timer
devices when removing the CPU. Otherwise, we will corrupt the device
list when re-registering the host timer on CPU onlining.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

linux/ipipe_base.h was originally designed to circumvment #include
hell by exporting only a subset of core definitions with minimum
dependencies to other inner headers.

The latest code reorganization fixed this issue in a better way, and
linux/ipipe.h is currently the only direct reader of
linux/ipipe_base.h, so let's merge both headers back as linux/ipipe.h.

Jan Kiszka authored Jan 31, 2019 and Philippe Gerum committed Nov 08, 2019

At least one arch, infamous x86, has a difference of NR_syscalls
depending on compat vs. native ABI. Account for that by introducing a
function that can deliver the currently valid syscall number if an arch
implements such a service. In all other cases, this change is
functionally no difference.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Jan Kiszka authored Nov 30, 2018 and Philippe Gerum committed Nov 08, 2019

This I-pipe hook reports the desired resumption mode to the subscriber:
resume all process tasks or just single-step a particular one? The use
case is to enable synchronous stopping / resuming of all head tasks of
a ptraced real-time process.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Jan Kiszka authored Nov 30, 2018 and Philippe Gerum committed Nov 08, 2019

A little bit inspired by the kernel's user return notifier, this
introduces an I-pipe hook before the kernel jumps back to a userspace
context from the root domain. The hook is design to allow a switch back
to the head domain, thus will not run through signal/preemption checks
when returning from the callback over head. It is guaranteed to fire on
return from interrupts and exceptions but may also fire on certain
syscall-return paths.

The first use case for the hook is resumption of ptraced tasks over
head if they were stopped in that domain.

This provides just the generic infrastructure, the invocation of
__ipipe_notify_user_intreturn as well as the definition of
TIP_USERINTRET are architecture-specific.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>