Skip to content

Add support for TIF_NOTIFY_SIGNAL

Jens Axboe io-uring lkml 1 version Applied

Status from this message: The following commit has been merged into the core/entry branch of tip:

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 0 repliesApplied

Changes since v6 from the cover letter

- Rebase to 5.10-rc1

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/4kernel: add task_sigpending() helperinclude/linux/sched/signal.h kernel/events/uprobes.c kernel/signal.c+12 -70 replies
2/4kernel: add support for TIF_NOTIFY_SIGNALarch/x86/kernel/signal.c include/linux/entry-common.h include/linux/entry-kvm.h +5 more+77 -110 replies
3/4x86: wire up TIF_NOTIFY_SIGNALarch/x86/include/asm/thread_info.h+2 -00 replies
4/4task_work: use TIF_NOTIFY_SIGNAL if availablekernel/task_work.c+29 -120 replies

Reviews trailers per patch

3 of 4 patches have a Reviewed-by or Acked-by.

PatchThomas GleixnerOleg Nesterov
1/4R-b R-b
2/4R-b
3/4
4/4R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCHSET v6a 0/4] Add support for TIF_NOTIFY_SIGNAL

Hi,

The goal is this patch series is to decouple TWA_SIGNAL based task_work from real signals and signal delivery. The motivation is speeding up TWA_SIGNAL based task_work, particularly for threaded setups where ->sighand is shared across threads. See the last patch for numbers.

On top of this I have an arch series that wires up TIF_NOTIFY_SIGNAL for all archs, and then procedes to kill off the legacy TWA_SIGNAL path, and the code associated with it.

Changes since v6:
- Rebase to 5.10-rc1

Signature · 1 line
Jens Axboe