On Thu, Mar 15, 2007 at 09:10:05PM +0800, Krishnappa Abhijith-A21204 wrote:
> In order to execute the system call in user space, the process is made
> to execute the system call switch on its kernel stack
> Why this is done... ?
Because all kernel code has to run on a kernel stack.
> Also UML qu
On Thu, Mar 15, 2007 at 10:29:28PM +0800, Krishnappa Abhijith-A21204 wrote:
> Can pls let me know why current->thread.forking = 1 was done before
> calling do_fork() and then reset after that ?
If you look at copy_thread, you will see that there is different
treatment for kernel threads and proces
replay
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techs
On Thu, Mar 15, 2007 at 11:19:37AM +0800, Krishnappa Abhijith-A21204 wrote:
> So Basically when we run a process in UML, the tracing thread enables
> tracing for that process.
You're talking about THE tracing thread. This is true if you're
referring to the obsolete tt mode of UML. However, now, t
Hi,
SORRY for bugging you guys so much...
Regarding fork() implementation in UML
I was going through the below code
long sys_fork(void)
{
long ret;
current->thread.forking = 1;
ret = do_fork(SIGCHLD, UPT_SP(¤t->thread.regs.regs),
¤t->thread.regs, 0, NULL, NULL);
curr
Hi,
I have a question regarding system call implementation on
Linux
In order to execute the system call in user space, the process is made
to execute the system call switch on its kernel stack
Why this is done... ?
Also UML queues a signal ( SIGUSR ) to the process in order to make
