public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: syscall_linkage
Date: Thu, 08 Apr 2004 16:23:43 +0000	[thread overview]
Message-ID: <20040408162342.GA21914@frankl.hpl.hp.com> (raw)
In-Reply-To: <407575C0.840593AC@nospam.org>

Hi,

On Thu, Apr 08, 2004 at 05:54:40PM +0200, Zoltan Menyhart wrote:
> Can somebody explain me, please, what the difference is between an
> __attribute__((syscall_linkage)) call and a regular one ?
> 

It indicates to the compiler that the arguments of the function 
are to be treated read-only. If they need to be modified, then a
copy is made into  other registers. This is necessary for the 
system call entry points because some syscalls can be restarted
and they need to restart we the orginal values. Remember that
all syscall arguments are passed in registers AND the registers
come straight from the user level, i.e., they are never copied.


> The Itanium Software Conventions & Runtime Architecture Guide does
> not say a word about it, does it mean it is a non standard way to
> pass parameters ?
> 
> What registers need / do not need to be saved with respect to what
> is written in the Intel book ?
> 
> Thanks,
> 
> Zoltán Menyhárt
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

-Stephane

  reply	other threads:[~2004-04-08 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 15:54 syscall_linkage Zoltan Menyhart
2004-04-08 16:23 ` Stephane Eranian [this message]
2004-04-08 23:39 ` syscall_linkage David Mosberger
2004-04-12 23:01 ` syscall_linkage Jim Wilson

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=20040408162342.GA21914@frankl.hpl.hp.com \
    --to=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox