summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorMiroslav Benes <mbenes@suse.cz>2017-02-14 02:42:34 +0100
committerJiri Kosina <jkosina@suse.cz>2017-03-08 09:22:40 +0100
commit2f09ca60a56dd9c217d32d68340e1b08cbbe1ace (patch)
tree15f594f9cb6cc851cd771a3dfc22c6cd32284b1e /include
parentlivepatch/s390: reorganize TIF thread flag bits (diff)
downloadlinux-2f09ca60a56dd9c217d32d68340e1b08cbbe1ace.tar.xz
linux-2f09ca60a56dd9c217d32d68340e1b08cbbe1ace.zip
livepatch/s390: add TIF_PATCH_PENDING thread flag
Update a task's patch state when returning from a system call or user space interrupt, or after handling a signal. This greatly increases the chances of a patch operation succeeding. If a task is I/O bound, it can be patched when returning from a system call. If a task is CPU bound, it can be patched when returning from an interrupt. If a task is sleeping on a to-be-patched function, the user can send SIGSTOP and SIGCONT to force it to switch. Since there are two ways the syscall can be restarted on return from a signal handling process, it is important to clear the flag before do_signal() is called. Otherwise we could miss the migration if we used SIGSTOP/SIGCONT procedure or fake signal to migrate patching blocking tasks. If we place our hook to sysc_work label in entry before TIF_SIGPENDING is evaluated we kill two birds with one stone. The task is correctly migrated in all return paths from a syscall. Signed-off-by: Miroslav Benes <mbenes@suse.cz> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions