linux-um archives
 help / color / mirror / Atom feed
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Young Koh <young.koh@gmail.com>,
	Blaisorblade <blaisorblade@yahoo.it>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Explaination of system call function flow in TT mode
Date: Wed, 18 May 2005 11:47:23 +0200	[thread overview]
Message-ID: <428B0F2B.3060503@fujitsu-siemens.com> (raw)
In-Reply-To: <20050517220053.GA10144@ccure.user-mode-linux.org>

Jeff Dike wrote:
> On Tue, May 17, 2005 at 01:56:55PM -0400, Young Koh wrote:
> 
>>the tracer (UML kernel) saves and restores the tracee's registers
>>using ptrace() in order to get syscall paramaters and save the return
>>value. while doing this, the tracer would need to care about only six
>>registers(eax, ebx, ecx, edx, esi, and edi) used for the syscall
>>parameter passing. I think, the tracer doesn't have to save all the
>>registers of the tracee, because the tracer will execute the syscall
>>for the tracee and the context of tracee will not be affected.
> 
> 
> This is true, but it's easier to get all of the GP registers than it is to
> selectively grab the syscall-related ones.
> 
> 
>>but, in arch/um/kernel/skas/process.c, move_registers() function gets
>>and sets even floating point registers, which i don't think will be
>>affected by the system call execution.
>>i tested and ran a UML kernel with the second ptrace() (used for
>>floating point registers) commented out, it seems to work. (probably
>>only for SKAS mode)
> 
> 
> Yeah, this is reasonable.  You have to be careful that you save and restore
> any registers that might be used by one of the stubs, but they don't use
> FP.
I also thought about not saving FP-regs on each kernel entry. But if you do
this optimization, you need to save / restore FP-regs on switch_to. Also you
need to get the FP-regs when setting up a signal-handler stackframe. And they
have to be restored on sys_(rt_)sigreturn from the values found in the
stackframe.
I hope, I didn't miss some other places that would need adaption.

As s390 can give me regs and FP-regs in one single ptrace call, I decided to
not do this optimization. Maybe for i386 and x86_64 it would be worth the cost.

	Bodo
> 
> 				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-18  9:47 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   ` [uml-devel] " Alex LIU
2005-02-03 19:38     ` 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 [this message]
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=428B0F2B.3060503@fujitsu-siemens.com \
    --to=bstroesser@fujitsu-siemens.com \
    --cc=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=young.koh@gmail.com \
    /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