Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

kthread_create_on_node(9) [centos man page]

KTHREAD_CREATE_ON_NO(9) 					   Driver Basics					   KTHREAD_CREATE_ON_NO(9)

kthread_create_on_node - create a kthread. SYNOPSIS
struct task_struct * kthread_create_on_node(int (*threadfn) (void *data), void * data, int node, const char namefmt[], ...); ARGUMENTS
threadfn the function to run until signal_pending(current). data data ptr for threadfn. node memory node number. namefmt[] printf-style name for the thread. ... variable arguments DESCRIPTION
This helper function creates and names a kernel thread. The thread will be stopped: use wake_up_process to start it. See also kthread_run. If thread is going to be bound on a particular cpu, give its node in node, to get NUMA affinity for kthread stack, or else give -1. When woken, the thread will run threadfn() with data as its argument. threadfn() can either call do_exit directly if it is a standalone thread for which no one will call kthread_stop, or return when 'kthread_should_stop' is true (which means kthread_stop has been called). The return value should be zero or a negative error number; it will be passed to kthread_stop. Returns a task_struct or ERR_PTR(-ENOMEM). COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 KTHREAD_CREATE_ON_NO(9)

Check Out this Related Man Page


utrace_prepare_examine - prepare to examine thread state SYNOPSIS
int utrace_prepare_examine(struct task_struct * target, struct utrace_engine * engine, struct utrace_examiner * exam); ARGUMENTS
target thread of interest, a struct task_struct pointer engine engine pointer returned by utrace_attach_task exam temporary state, a struct utrace_examiner pointer DESCRIPTION
This call prepares to safely examine the thread target using struct user_regset calls, or direct access to thread-synchronous fields. When target is current, this call is superfluous. When target is another thread, it must held stopped via UTRACE_STOP by engine. This call may block the caller until target stays stopped, so it must be called only after the caller is sure target is about to unschedule. This means a zero return from a utrace_control call on engine giving UTRACE_STOP, or a report_quiesce or report_signal callback to engine that used UTRACE_STOP in its return value. Returns -ESRCH if target is dead or -EINVAL if UTRACE_STOP was not used. If target has started running again despite UTRACE_STOP (for SIGKILL or a spurious wakeup), this call returns -EAGAIN. When this call returns zero, it's safe to use struct user_regset calls and task_user_regset_view on target and to examine some of its fields directly. When the examination is complete, a utrace_finish_examine call must follow to check whether it was completed safely. Kernel Hackers Manual 2.6. July 2010 UTRACE_PREPARE_EXAMI(9)
Man Page