All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@redhat.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: eric@cisu.net, linux-kernel@vger.kernel.org
Subject: Re: Quick Syscall question
Date: Sun, 05 Sep 2004 18:17:04 -0400	[thread overview]
Message-ID: <413B9060.9060500@redhat.com> (raw)
In-Reply-To: <20040905113114.313efdf2.rddunlap@osdl.org>

Randy.Dunlap wrote:

>On Sun, 5 Sep 2004 13:17:42 -0500 Eric Bambach wrote:
>
>| Hello,
>| 
>| 	This may seem like a silly question, however we were all beginning 
>| programmers once ;)
>| 
>| 	I want to do some manipulating of network interfaces and routing and such. I 
>| am reading through some of the linux net sources but am confused on what are 
>| internal, kernel-only functions and what are externally visable syscalls. How 
>| can I tell from the source what is user-space visable that I can hook into 
>| and what is intternel stuff? Should I just be looking at headers or do I have 
>| to delve into the .c sources? I can do either, I just need a pointer on where 
>| to start and what I should be looking for.
>
>Most syscalls are listed in include/linux/syscalls.h.
>Also look in include/asm-*/unistd.h.
>Also in entry.S in arch/*/ (various sub-directory levels).
>
>--
>~Randy
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>
Also, if you're looking into writing kernel modules, anything listed in 
arch/*ksyms.c as a symbol inside an EXPORT_SYMBOL block is accessible, 
although that may not mean its available from user space.
Neil

-- 
/***************************************************
 *Neil Horman
 *Software Engineer
 *Red Hat, Inc.
 *nhorman@redhat.com
 *gpg keyid: 1024D / 0x92A74FA1
 *http://pgp.mit.edu
 ***************************************************/


      reply	other threads:[~2004-09-05 22:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 18:17 Quick Syscall question Eric Bambach
2004-09-05 18:31 ` Randy.Dunlap
2004-09-05 22:17   ` Neil Horman [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=413B9060.9060500@redhat.com \
    --to=nhorman@redhat.com \
    --cc=eric@cisu.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /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.