All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Alex LIU <alex.liu@st.com>
Cc: UML-dev <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Question about the kernel thread in UML TT mode
Date: Tue, 17 May 2005 11:53:57 -0400	[thread overview]
Message-ID: <20050517155357.GA5872@ccure.user-mode-linux.org> (raw)
In-Reply-To: <006101c55ac4$2ccbf0e0$9eb3c68a@SHZ.ST.COM>

On Tue, May 17, 2005 at 05:38:21PM +0800, Alex LIU wrote:
> In UML,when do_fork was called,the new process P will be created in UML. Then in copy_thread_tt(in fact in start_fork_tramp)the corresponding process Q will be created in the host linux. I know the pid of the corresponding host process Q is appointed as the extern_pid of the UML process P. But then how will the 2 processes do next individually?

They aren't really two processes.  But they set up signal handlers, and the 
timer, and then go to sleep until that process is scheduled.

> In UML,the function copy_thread_tt call start_fork_tramp, which cloned a thread. Once the thread was created it will run the outer_tramp function,in which cloned another thread. Once the second thread was created it will run the tramp function(fork_tramp or new_thread_proc). In fact the first thread is a temp one.it will kill itself later.Then why does UML clone 2 threads in copy_thread_tt?

To avoid zombies - the parent process is expected to reap exited children,
but as far as UML is concerned, the parent may not wake up for along time,
leaving the child as a zombie for an arbitrary time.

The two threads are the double-fork trick.  The parent of the new process
is the first temporary thread, which exits immediately, leaving the new child
to be inherited by init, which will reap children immediately, eliminating 
zombies.

> In UML,when the kernel_thread was called,the UML kernel thread P will be created in copy_process. And the corresponding host thread Q will be create in copy_thread_tt. Then the host thread Q will run its SIGUSR1 signal handler new_thread_handler,which will call run_kernel_thread function and exited at last. But I think it should be the UML kernel thread P that call run_kernel_thread function, any problems? 

P and Q are the same thing, so it makes no sense to say the handler should be
run in one rather than the other.

				Jeff


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-05-17 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  9:38 [uml-devel] Question about the kernel thread in UML TT mode Alex LIU
2005-05-17 15:53 ` Jeff Dike [this message]
     [not found]   ` <000e01c55b91$039466d0$9eb3c68a@SHZ.ST.COM>
2005-05-18 13:31     ` Jeff Dike
     [not found] <000c01c55c59$37dd1e50$9eb3c68a@SHZ.ST.COM>
2005-05-19 13:31 ` Blaisorblade
2005-05-19 14:56   ` Jeff Dike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050517155357.GA5872@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=alex.liu@st.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.