Linux Kernel Threads in Device Drivers

來源:互聯網
上載者:User
文章目錄
  • kthread.h
  • kthread.c
  • thread_drv.c
  • Makefile

Purpose

This examples shows how to create and stop a kernel thread.
The driver is implemented as a loadable module. In the init_module() routine five kernel threads are created. This kernel threads sleep one second, wake up, print a message and fall asleep again. On unload of the module (cleanup_module), the kernel threads are killed.
The example has been tested with linuxkernel 2.4.2 on Intel (uni processor only) and Alpha platform (COMPAQ Personal Workstation 500au (uni processor), DS20 and ES40 (SMP).

A version for the 2.2 kernel can be found here. Note: depending on the context of the creator of the threads the new threads may inherit properties from the parent you do not want to have. The new version avoids this by having keventd create the threads. The 2.2. kernel do not have a keventd, so this approach is not implementable there.

Functions in example
  • start_kthread: creates a new kernel thread. Can be called from any process context but not from interrupt. The functions blocks until the thread started.
  • stop_kthread: stop the thread. Can be called from any process context but the thread to be terminated. Cannot be called from interrupt context. The function blocks until the thread terminated.
  • init_kthread: sets the environment of the new threads. Is to be called out of the created thread.
  • exit_kthread: needs to be called by the thread to be terminated on exit
Creation of new Thread

A new thread is created with kernel_thread(). The thread inherits properties from its parents. To make sure that we do not get any weired properties, we let keventd create the new thread.
The new thread is created with start_kthread(). It uses a semaphore to block until the new thread is running. A down() blocks the start_kthread() routine until the corresponding up() call in init_kthread() is executed.
The new thread must call init_kthread()in order to let the creator continue.

Stop of new Thread

stop_kthread() sets a flag that the thread uses to determine whether do die or not and sends a SIGKILL to the thread. This signal causes the thread to be woken up. On wakeup it will check for the flag and then terminate itself by calling exit_kthread and returning from the thread function. With a semaphore the stop_kthread()function blocks until the thread terminated.

Initialization of new Thread

Within the new created thread, init_kthread() needs to be called. This function sets a signal mask, initialises a wait queue, the termination flag and sets a new name for the thread. With a up()call it notifies the creator that the setup is done.

Exit of new Thread

When the thread receives the notification to terminate itself, is calls the exit_kthread() function. It notifies the stop_kthread() function that it terminated with an up()call.

The new Thread itself

The new thread is implemented in the example_thread() function. It runs an endless loop (for(;;)). In the loop it falls asleep with the interruptible_sleep_on_timeout() function. It comes out of this function either when the timeout expires or when a signal got caught.
The "work" in the thread is to print out a message with printk.

Kernel Versions

The example has been tested on 2.4.2.

Example Device Driver Code

The example consists of four files: kthread.h, kthread.c, thread_drv.c and a Makefile

kthread.h
#ifndef _KTHREAD_H#define _KTHREAD_H#include <linux/config.h>#include <linux/version.h>#include <linux/kernel.h>#include <linux/sched.h>#include <linux/tqueue.h>#include <linux/wait.h>#include <asm/unistd.h>#include <asm/semaphore.h>/* a structure to store all information we need   for our thread */typedef struct kthread_struct{        /* private data */        /* linux task structure of thread */        struct task_struct *thread;        /* Task queue need to launch thread */        struct tq_struct tq;        /* function to be started as thread */        void (*function) (struct kthread_struct *kthread);        /* semaphore needed on start and creation of thread. */        struct semaphore startstop_sem;        /* public data */        /* queue thread is waiting on. Gets initialized by           init_kthread, can be used by thread itself.        */        wait_queue_head_t queue;        /* flag to tell thread whether to die or not.           When the thread receives a signal, it must check           the value of terminate and call exit_kthread and terminate           if set.        */        int terminate;        /* additional data to pass to kernel thread */        void *arg;} kthread_t;/* prototypes *//* start new kthread (called by creator) */void start_kthread(void (*func)(kthread_t *), kthread_t *kthread);/* stop a running thread (called by "killer") */void stop_kthread(kthread_t *kthread);/* setup thread environment (called by new thread) */void init_kthread(kthread_t *kthread, char *name);/* cleanup thread environment (called by thread upon receiving termination signal) */void exit_kthread(kthread_t *kthread);#endif
kthread.c
#include <linux/config.h>#include <linux/version.h>#if defined(MODVERSIONS)#include <linux/modversions.h>#endif#include <linux/kernel.h>#include <linux/sched.h>#include <linux/tqueue.h>#include <linux/wait.h>#include <linux/signal.h>#include <asm/semaphore.h>#include <asm/smplock.h>#include "kthread.h"/* private functions */static void kthread_launcher(void *data){        kthread_t *kthread = data;        kernel_thread((int (*)(void *))kthread->function, (void *)kthread, 0);        }/* public functions *//* create a new kernel thread. Called by the creator. */void start_kthread(void (*func)(kthread_t *), kthread_t *kthread){        /* initialize the semaphore:           we start with the semaphore locked. The new kernel           thread will setup its stuff and unlock it. This           control flow (the one that creates the thread) blocks           in the down operation below until the thread has reached           the up() operation.         */        init_MUTEX_LOCKED(&kthread->startstop_sem);        /* store the function to be executed in the data passed to           the launcher */        kthread->function=func;                /* create the new thread my running a task through keventd */        /* initialize the task queue structure */        kthread->tq.sync = 0;        INIT_LIST_HEAD(&kthread->tq.list);        kthread->tq.routine =  kthread_launcher;        kthread->tq.data = kthread;        /* and schedule it for execution */        schedule_task(&kthread->tq);        /* wait till it has reached the setup_thread routine */        down(&kthread->startstop_sem);               }/* stop a kernel thread. Called by the removing instance */void stop_kthread(kthread_t *kthread){        if (kthread->thread == NULL)        {                printk("stop_kthread: killing non existing thread!/n");                return;        }        /* this function needs to be protected with the big   kernel lock (lock_kernel()). The lock must be           grabbed before changing the terminate   flag and released after the down() call. */        lock_kernel();                /* initialize the semaphore. We lock it here, the           leave_thread call of the thread to be terminated           will unlock it. As soon as we see the semaphore           unlocked, we know that the thread has exited.*/        init_MUTEX_LOCKED(&kthread->startstop_sem);        /* We need to do a memory barrier here to be sure that           the flags are visible on all CPUs.         */        mb();        /* set flag to request thread termination */        kthread->terminate = 1;        /* We need to do a memory barrier here to be sure that           the flags are visible on all CPUs.         */        mb();        kill_proc(kthread->thread->pid, SIGKILL, 1);               /* block till thread terminated */        down(&kthread->startstop_sem);        /* release the big kernel lock */        unlock_kernel();        /* now we are sure the thread is in zombie state. We           notify keventd to clean the process up.        */        kill_proc(2, SIGCHLD, 1);}/* initialize new created thread. Called by the new thread. */void init_kthread(kthread_t *kthread, char *name){        /* lock the kernel. A new kernel thread starts without           the big kernel lock, regardless of the lock state           of the creator (the lock level is *not* inheritated)        */        lock_kernel();        /* fill in thread structure */        kthread->thread = current;        /* set signal mask to what we want to respond */        siginitsetinv(&current->blocked, sigmask(SIGKILL)|sigmask(SIGINT)|sigmask(SIGTERM));        /* initialise wait queue */        init_waitqueue_head(&kthread->queue);        /* initialise termination flag */        kthread->terminate = 0;        /* set name of this process (max 15 chars + 0 !) */        sprintf(current->comm, name);                /* let others run */        unlock_kernel();        /* tell the creator that we are ready and let him continue */        up(&kthread->startstop_sem);}/* cleanup of thread. Called by the exiting thread. */void exit_kthread(kthread_t *kthread){        /* we are terminating *//* lock the kernel, the exit will unlock it */        lock_kernel();        kthread->thread = NULL;        mb();        /* notify the stop_kthread() routine that we are terminating. */up(&kthread->startstop_sem);/* the kernel_thread that called clone() does a do_exit here. *//* there is no race here between execution of the "killer" and real termination   of the thread (race window between up and do_exit), since both the   thread and the "killer" function are running with the kernel lock held.   The kernel lock will be freed after the thread exited, so the code   is really not executed anymore as soon as the unload functions gets   the kernel lock back.   The init process may not have made the cleanup of the process here,   but the cleanup can be done safely with the module unloaded.*/}
thread_drv.c
#include <linux/config.h>#include <linux/version.h>#include <linux/module.h>#if defined(MODVERSIONS)#include <linux/modversions.h>#endif#include <linux/kernel.h>#include <linux/string.h>#include <linux/errno.h>#include <linux/sched.h>#include "kthread.h"#define NTHREADS 5/* the variable that contains the thread data */kthread_t example[NTHREADS];/* prototype for the example thread */static void example_thread(kthread_t *kthread);/* load the module */int init_module(void){        int i;                /* create new kernel threads */for (i=0; i <NTHREADS; i++)                start_kthread(example_thread, &example[i]);                return(0);}/* remove the module */void cleanup_module(void){        int i;                /* terminate the kernel threads */for (i=0; i<NTHREADS; i++)                stop_kthread(&example[i]);                return;}/* this is the thread function that we are executing */static void example_thread(kthread_t *kthread){        /* setup the thread environment */        init_kthread(kthread, "example thread");                printk("hi, here is the kernel thread/n");                /* an endless loop in which we are doing our work */        for(;;)        {                /* fall asleep for one second */                interruptible_sleep_on_timeout(&kthread->queue, HZ);                /* We need to do a memory barrier here to be sure that                   the flags are visible on all CPUs.                 */                 mb();                                /* here we are back from sleep, either due to the timeout                   (one second), or because we caught a signal.                */                if (kthread->terminate)                {                        /* we received a request to terminate ourself */                        break;                    }                                /* this is normal work to do */                printk("example thread: thread woke up/n");        }        /* here we go only in case of termination of the thread */        /* cleanup the thread, leave */        exit_kthread(kthread);/* returning from the thread here calls the exit functions */}
Makefile
# set to your kernel treeKERNEL  = /usr/src/linux# get the linux architecture. Needed to find proper include file for CFLAGSARCH=$(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/)# set default flags to compile moduleCFLAGS = -D__KERNEL__ -DMODULE -I$(KERNEL)/includeCFLAGS+= -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasingall:thread_mod.o# get configuration of kernelinclude $(KERNEL)/.config# modify CFLAGS with architecture specific flagsinclude $(KERNEL)/arch/${ARCH}/Makefile# enable the module versions, if configured in kernel source treeifdef CONFIG_MODVERSIONSCFLAGS+= -DMODVERSIONS -include $(KERNEL)/include/linux/modversions.hendif# enable SMP, if configured in kernel source treeifdef CONFIG_SMPCFLAGS+= -D__SMP__endif# note: we are compiling the driver object file and then linking# we link it into the module. With just one object file as in# this example this is not needed. We can just load the object# file produced by gcc # link the thread driver modulethread_mod.o:     thread_drv.o kthread.old -r -o thread_mod.o thread_drv.o kthread.o# compile the kthread object filekthread.o:kthread.c kthread.hgcc $(CFLAGS) -c kthread.c# compile the thread driverthread_drv.o:     thread_drv.c kthread.hgcc $(CFLAGS) -c thread_drv.cclean:rm -f *.o
Bugs

The code assumes that keventdis running with PID 2.

Comments, Corrections

Please send comments, corrections etc. to the address below.  
http://blog.csdn.net/relianceslee/archive/2006/07/21/952829.aspx
http://blog.csdn.net/absurd/archive/2006/07/25/976820.aspx

上一篇:《TCP/IP網路基礎》

相關文章

聯繫我們

該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.