From: Michael Ellerman <michael@ellerman.id.au>
To: David Laight <David.Laight@ACULAB.COM>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: RE: pread() and pwrite() system calls
Date: Tue, 29 May 2012 18:54:23 +1000 [thread overview]
Message-ID: <1338281663.15519.2.camel@concordia> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B6F29@saturn3.aculab.com>
On Tue, 2012-05-29 at 09:28 +0100, David Laight wrote:
> > > A special pread/pwrite asm stub that just copies
> > > r7 to r0 could be used.
> > >
> > > Would it be enough to do:
> > > syscall_pread_pwrite:
> > > mov 0,7
> > > sc
> > > blr
> > > and handle the -ve -> errno in C?
> >
> > Huh? Won't fly, r0 is used for the system call number!
>
> I was copying that from r7!
Using the non-existant 'mov' instruction!
or 0,7,7
is much clearer :)
cheers
next prev parent reply other threads:[~2012-05-29 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 13:29 pread() and pwrite() system calls David Laight
2012-05-25 16:45 ` Gabriel Paubert
2012-05-29 8:28 ` David Laight
2012-05-29 8:54 ` Michael Ellerman [this message]
2012-05-30 10:56 ` David Laight
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=1338281663.15519.2.camel@concordia \
--to=michael@ellerman.id.au \
--cc=David.Laight@ACULAB.COM \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).