Jens Axboe 91989c7078 task_work: cleanup notification modes ... A previous commit changed the notification mode from true/false to an int, allowing notify-no, notify-yes, or signal-notify. This was backwards compatible in the sense that any existing true/false user would translate to either 0 (on notification sent) or 1, the latter which mapped to TWA_RESUME. TWA_SIGNAL was assigned a value of 2. Clean this up properly, and define a proper enum for the notification mode. Now we have: - TWA_NONE. This is 0, same as before the original change, meaning no notification requested. - TWA_RESUME. This is 1, same as before the original change, meaning that we use TIF_NOTIFY_RESUME. - TWA_SIGNAL. This uses TIF_SIGPENDING/JOBCTL_TASK_WORK for the notification. Clean up all the callers, switching their 0/1/false/true to using the appropriate TWA_* mode for notifications. Fixes: e91b481623 ("task_work: teach task_work_add() to do signal_wake_up()") Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Jens Axboe <axboe@kernel.dk>		2020-10-17 15:05:30 -06:00
..
callchain.c	uaccess: add force_uaccess_{begin,end} helpers	2020-08-12 10:57:59 -07:00
core.c	These are the performance events changes for v5.10:	2020-10-12 14:14:35 -07:00
hw_breakpoint.c	powerpc/watchpoint: Don't allow concurrent perf and ptrace events	2020-05-19 00:14:45 +10:00
internal.h	perf/core: Replace zero-length array with flexible-array	2020-05-19 20:34:16 +02:00
Makefile
ring_buffer.c	perf: Make struct ring_buffer less ambiguous	2020-01-13 13:19:38 -05:00
uprobes.c	task_work: cleanup notification modes	2020-10-17 15:05:30 -06:00