From: Alex LIU <alex.liu@st.com>
To: 'Blaisorblade' <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] RE: Explaination of system call function flow in TT mode
Date: Wed, 2 Feb 2005 23:29:59 +0800 [thread overview]
Message-ID: <021201c5093c$0ec75780$ac655e0a@sha.st.com> (raw)
In-Reply-To: <200501282010.50020.blaisorblade@yahoo.it>
Hi,Blaisorblade. You wrote:
>do_syscall is called, and then this is done:
>
> sig = SIGUSR2;
> tracing = 0;
>... after, this saves the new tracing value inside "task", which is a struct
>task_struct.
>
> set_tracing(task, tracing);
>
But what's the exact meaning of the task in the tracer function? It is defined as:
task = cpu_tasks[proc_id].task
Is it the task struct of the traced thread?
What's the difference between "task->pid" and "task->thread.mode.tt.extern_pid"?
I know in TT mode every thread in UML will has a corresponding thread in host. But I don't know the exact relationship between them. And I didn't found how UML creat the corresponding thread in host.
Thanks a lot!
Alex
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-02-02 15:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003e01c503b3$f3e46cb0$ac655e0a@sha.st.com>
2005-01-28 19:10 ` [uml-devel] Explaination of system call function flow in TT mode Blaisorblade
2005-02-02 15:29 ` Alex LIU [this message]
2005-02-03 19:38 ` [uml-devel] " Blaisorblade
2005-05-16 14:08 ` [uml-devel] " Young Koh
2005-05-16 17:08 ` Blaisorblade
2005-05-16 18:52 ` Young Koh
2005-05-16 20:52 ` Jeff Dike
2005-05-16 21:24 ` Blaisorblade
2005-05-17 0:09 ` Young Koh
2005-05-17 0:17 ` Blaisorblade
2005-05-17 17:56 ` Young Koh
2005-05-17 22:00 ` Jeff Dike
2005-05-18 9:47 ` Bodo Stroesser
2005-05-18 13:24 ` Young Koh
2005-05-18 14:57 ` Blaisorblade
2005-05-18 15:09 ` Jeff Dike
2005-05-18 15:26 ` Bodo Stroesser
2005-05-18 15:03 ` Jeff Dike
2005-05-18 13:33 ` Jeff Dike
2005-05-18 15:20 ` Bodo Stroesser
2005-05-18 15:28 ` Blaisorblade
2006-02-09 22:08 ` Young Koh
2006-02-09 23:38 ` 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='021201c5093c$0ec75780$ac655e0a@sha.st.com' \
--to=alex.liu@st.com \
--cc=blaisorblade@yahoo.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox