From: "Aneesh Kumar K.V" <aneesh.kumar@digital.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>
Cc: "Helgaas, Bjorn (HP)" <bjorn.helgaas@hp.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-ia64@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4 force_successful_syscall()
Date: 18 Sep 2003 11:12:21 +0530 [thread overview]
Message-ID: <1063863741.1801.34.camel@satan.xko.dec.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0309171659510.3994-100000@logos.cnet>
On Thu, 2003-09-18 at 01:30, Marcelo Tosatti wrote:
> On Wed, 10 Sep 2003, Bjorn Helgaas wrote:
>
> > Here's a 2.4 backport of this change to 2.5:
> >
> >
> http://linux.bkbits.net:8080/linux-2.5/cset@1.1046.238.7?nav=index.html
> >
> > Alpha, ppc, and sparc64 define force_successful_syscall_return() in
> 2.5,
> > but since it's not obvious to me how to do it correctly in 2.4, I left
> > them unchanged.
>
> Whats the reasoning behing this patch?
IIRC those changes were added to 2.5 by David. Architecture like Ia64
and Alpha support error return via a different register set ( $19 for
Alpha ). But syscalls like ptrace can have negative return value for
successful returns. So in that particular case $19 is forced to be zero
to indicate it is a successful return. IIUC
force_successful_syscall_return is a wrapper around doing that. On
alpha actually r0 in the stack (regs.r0 ) is made zero which is read in
entry.S and put in $19.
-aneesh
next prev parent reply other threads:[~2003-09-18 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200309101626.48541.bjorn.helgaas@hp.com>
2003-09-17 20:00 ` Marcelo Tosatti
2003-09-17 21:41 ` Bjorn Helgaas
2003-09-18 5:42 ` Aneesh Kumar K.V [this message]
2003-09-18 6:01 ` Aneesh Kumar K.V
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=1063863741.1801.34.camel@satan.xko.dec.com \
--to=aneesh.kumar@digital.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®