linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Krishnappa Abhijith-A21204 <abhijith@motorola.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Regarding getpid
Date: Tue, 12 Dec 2006 09:46:48 -0500	[thread overview]
Message-ID: <20061212144648.GA4093@ccure.user-mode-linux.org> (raw)
In-Reply-To: <0A01463223B8164194908CAC85B66A1201324F53@ZMY16EXM67.ds.mot.com>

On Tue, Dec 12, 2006 at 06:12:24PM +0800, Krishnappa Abhijith-A21204 wrote:
> Ok Thanks. So actually getpid() doesn't cause mode switch.

Sure it does.  Any system call does.

> But is it mandatory to execute  getpid()? If yes why

That's the way ptrace traditionally works.  PTRACE_SYSEMU, which came later
avoids the need to invoke some system call.  It just nullifies the system
call in the expectation that the tracer will emulate it.

				Jeff

-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
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.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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:[~2006-12-12 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  4:26 [uml-devel] Regarding getpid Krishnappa Abhijith-A21204
2006-12-12  9:49 ` Geert Uytterhoeven
2006-12-12 10:12   ` Krishnappa Abhijith-A21204
2006-12-12 14:46     ` Jeff Dike [this message]

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=20061212144648.GA4093@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=abhijith@motorola.com \
    --cc=geert@linux-m68k.org \
    --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