On Tue, Aug 17, 2010 at 10:45 PM, nascent mind nascent.m...@gmail.com wrote:
Hi,
I am trying to understand the boot process of the kernel and I am not
able to understand why the stack segment should be equal to the data segment
here
I wrote following program in my home directory.
#include linux/kernel.h
#include sys/syscall.h
#include linux/module.h
extern void *sys_table[];
asmlinkage int(*main_sys_exit)(int);
{
printk(Sys_exit called with err_code=%d\n,err_code);
return main_sys_exit(err_code);
}
int
Hi Taps,
On Wed, Aug 18, 2010 at 9:12 AM, Tapas Mishra mightydre...@gmail.com wrote:
I wrote following program in my home directory.
...snip...
gcc -Wall -DMODULE -D__KERNEL__ -DLINUX -c sample2.c[/code]
...snip...
What is the above error and why is it coming?
I did all this in my home
Hi,
For a critical section protected by a spin lock, kernel preemption is
disabled explicitly, probably to make the critical section atomic.
But, suppose that an interrupt occures in this critical section,
allowing interrupts can wreck the atomicity. So, why don't we disable
interrupts as a
Hello,
On Wed, Aug 18, 2010 at 8:07 PM, Parmenides mobile.parmeni...@gmail.com wrote:
Hi,
For a critical section protected by a spin lock, kernel preemption is
disabled explicitly, probably to make the critical section atomic.
But, suppose that an interrupt occures in this critical section,
