Linux Device Drivers(3rd Edition)--reading digest

1. Does interupt belong to kernel space?

Unix transfers execution from user space to kernel space whenever an application issues a system call or is suspended by a hardware interrupt. Kernel code executing a system call is working in the context of a  rocess—it operates on behalf of the calling process and is able to access data in the process’s address space. Code that handles interrupts, on the other hand, is asynchronous with respect to processes and is not related to any particular process. 

2. What is the role of module?

The role of a module is to extend kernel functionality; modularized code runs in kernel space.

3. What are the three classes of devices and modules?

character devices, block devices, network interface

4. How to print kernel message to terminal?

vi /etc/syslog.conf

open "kern.*                                                 /dev/console"

cd /etc/init.d/

"./syslog restart" to restart syslogd and klogd

But if failed in Fedora 4.0 in VMWare !!!???

------------------------------------------------------------------------------------------------------------------------

Maybe It is the answer:

If the priority is less than the integer variable console_loglevel, the message is delivered to the console one line at a time (nothing is sent unless a trailing newline is provided). If both klogd and syslogd are running on the system, kernel messages are appended to /var/log/messages (or otherwise treated depending on your syslogd configuration), independent of console_loglevel. If klogd is not running, the message won’t reach user space unless you read /proc/kmsg (which is often most easily done with the dmesg command).

5. How to explain it in makefile?

If, instead, you have a module called module.ko that is generated from two source
files (called, say, file1.c and file2.c), the correct incantation would be:
obj-m := module.o
module-objs := file1.o file2.o

make -C ~/kernel-2.6 M=`pwd` modules
This command starts by changing its directory to the one provided with the -C
option (that is, your kernel source directory). There it finds the kernel’s top-level
makefile. The M= option causes that makefile to move back into your module source
directory before trying to build the modules target. This target, in turn, refers to the list
of modules found in the obj-m variable, which we’ve set to module.o in our examples.