Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Carsten Langgaard <carstenl@mips.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: LTP testing
Date: Tue, 25 Jun 2002 16:39:41 +0200	[thread overview]
Message-ID: <20020625163941.A19360@dea.linux-mips.net> (raw)
In-Reply-To: <3D186E76.63B33B0E@mips.com>; from carstenl@mips.com on Tue, Jun 25, 2002 at 03:21:58PM +0200

On Tue, Jun 25, 2002 at 03:21:58PM +0200, Carsten Langgaard wrote:

> The problem is that the code is called with $a0 = 0. So the 'sw v0,
> 0(a0)' after the syscall generates a segmentation fault.
> Why are the pipe syscall implemented this way, where we return the two
> descriptors in v0 and v1 ?
> Why doesn't the kernel do these stores (this way we can do an access
> check, like i386 does) ?

Because the interface we're using here is even lighter, even faster.  Note
that by the time when I decieded to use this interface this was potencially
a huge difference as verify_area() was searching the mm AVL trees, so this
interface was potenciall much faster by that time.

  Ralf

  parent reply	other threads:[~2002-06-25 14:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 13:21 LTP testing Carsten Langgaard
2002-06-25 13:53 ` Maciej W. Rozycki
2002-06-25 14:18   ` Carsten Langgaard
2002-06-25 14:56     ` Maciej W. Rozycki
2002-06-25 15:06       ` Carsten Langgaard
2002-06-25 15:28         ` Ralf Baechle
2002-06-25 14:28   ` Johannes Stezenbach
2002-06-25 14:39 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-25 10:47 Carsten Langgaard
2002-06-25  9:59 Carsten Langgaard
2002-06-25 12:07 ` Maciej W. Rozycki
2002-06-25  7:15 Carsten Langgaard
2002-06-25 13:59 ` 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=20020625163941.A19360@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=carstenl@mips.com \
    --cc=linux-mips@oss.sgi.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