From: Terje Eggestad <terje.eggestad@scali.com>
To: Amber Palekar <amber_palekar@yahoo.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Again:syscall from modules
Date: 27 Dec 2001 16:54:25 +0100 [thread overview]
Message-ID: <1009468465.15846.0.camel@eggis1> (raw)
In-Reply-To: <20011225131441.60811.qmail@web20306.mail.yahoo.com>
In-Reply-To: <20011225131441.60811.qmail@web20306.mail.yahoo.com>
Yes, the sys_* funcs are declared asmlinkage int sys_*.
where the asmlinkage differ from platform to platform.
It's used to tell the compiler if a non standared calling
convertion is used, typically if params are passed by registers
instead of stack. The asmlinkage define must be sett according to the
syscall dispatcher (entry.S on ia32), and may be changed accordingly.
In short, if you want to use sys_* you must understand the interaction
between the sys_* funcs and the dispatcher on *every* platform, and
the interaction may change without notice.
In short short, don't don't don't don't use the sys_* functions.
TJ
On Tue, 2001-12-25 at 14:14, Amber Palekar wrote:
>
> Hi,
>
> > Just use sock_sendmsg() and sock_recvmsg() directly.
> > They are both
> > exported in netsyms.c.
> Is there any specific reason behind not exporting
> sys_sendto and sys_recvfrom ??
>
> > Cheers,
> > Trond
>
> TIA
> Amber
>
>
> __________________________________________________
> Do You Yahoo!?
> Send your FREE holiday greetings online!
> http://greetings.yahoo.com
> -
> 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/
next prev parent reply other threads:[~2001-12-27 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 11:31 syscall from modules Amber Palekar
2001-12-25 13:09 ` Trond Myklebust
2001-12-25 13:14 ` Again:syscall " Amber Palekar
2001-12-25 18:37 ` Trond Myklebust
2001-12-27 15:54 ` Terje Eggestad [this message]
2001-12-27 16:04 ` Terje Eggestad
2001-12-27 18:57 ` Trond Myklebust
2001-12-28 15:41 ` Ralf Baechle
2001-12-28 15:48 ` Trond Myklebust
2001-12-28 16:26 ` Ralf Baechle
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=1009468465.15846.0.camel@eggis1 \
--to=terje.eggestad@scali.com \
--cc=amber_palekar@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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