linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: sathish.j@tatainfotech.com (SATHISH.J)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reg:flow of system call in linux
Date: Sun, 12 Aug 2001 15:10:38 +0100 (BST)	[thread overview]
Message-ID: <E15Vvwt-0005m5-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.10.10108121903130.26368-100000@blrmail> from "SATHISH.J" at Aug 12, 2001 07:05:35 PM

> Can someone tell me about the flow of system call for eg. from open
> wrapper routine to sys_open() function or atleast please suggest me a
> book/website
> where I can get this info.

Userspace open() calls into glibc code
glibc does architecture dependant magic to make a syscall
The kernel syscall code does architecture dependant magic 
The kernel calls sys_open


In the x86 case the magic is basically

Load arguments into the right registers
int 0x80

then the kernel code in arch/i386/kernel/entry.S


  reply	other threads:[~2001-08-12 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-01 14:37 Reg crash utility installation SATHISH.J
2001-07-02 22:19 ` Patrick O'Rourke
2001-07-03  8:52 ` Reg kdb utility SATHISH.J
2001-07-03 10:39   ` Balbir Singh
2001-08-02  9:37   ` Reg char device driver on linux SATHISH.J
2001-08-12 13:35   ` Reg:flow of system call in linux SATHISH.J
2001-08-12 14:10     ` Alan Cox [this message]
2001-08-13  5:22     ` Reg System.map file SATHISH.J
2001-08-13  5:16       ` Keith Owens
2001-08-21  9:02       ` Reg core dump of KDE-2 SATHISH.J
2001-08-21 14:29         ` Ignacio Vazquez-Abrams
2001-08-23 12:59         ` command source code SATHISH.J

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=E15Vvwt-0005m5-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sathish.j@tatainfotech.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;
as well as URLs for NNTP newsgroup(s).