when interrupt occurs, what is the sequence of steps that are performed by linux.
i know kernel leaves the work it is presently doing and switches to interrupt handler to handle that interrupt.
ON x86, the hardware does a lookup in the IDT, saves registers on the stack & passes control to the interrupt handler.
But it want to know the activities in terms of system calls that occur during that activity?
System calls do not come into the picture.
...
Suppose we have a module in which system calls are trapped by changing system call table pointer. Thus before the actual system call, my module is called. In this module some simple activities are performed like printing information, like process id and it's name or, in some case i may also store this information in some data structure i use, and then actual system call is called within that module.
Calling of actual system call is done so that functionality of kernel is not affected.
Now in this thing if the situation described above comes, i.e.
If a process is running on one terminal and if i click with mouse on panel bar to invoke another terminal, on KDE desktop, what happens? i mean in terms of system calls.
What has this got to do anything with the kernel ? Why should the kernel be concerned about KDE, panels & terminals ?
--Swapnil
-- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
