From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] sys_indirect kernel implementation for PowerPC
Date: Tue, 20 Nov 2007 22:45:34 -0600 [thread overview]
Message-ID: <53FD3FB3-960E-48B8-8FF3-8233FDCD5B61@kernel.crashing.org> (raw)
In-Reply-To: <18243.41278.72798.100000@cargo.ozlabs.ibm.com>
On Nov 20, 2007, at 9:08 PM, Paul Mackerras wrote:
> This implements sys_indirect for 32-bit and 64-bit powerpc machines,
> including a 32-bit compatibility implementation for 64-bit powerpc.
> I decided to use assembly language for call_syscall because on 64-bit
> powerpc the system call table has the addresses of the function text
> rather than pointers to function descriptors; hence the system call
> functions can't be called from C via the system call table.
Admit it you were bored and wanted to write some PPC asm ;)
- k
prev parent reply other threads:[~2007-11-21 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 3:08 [PATCH] sys_indirect kernel implementation for PowerPC Paul Mackerras
2007-11-21 3:29 ` Stephen Rothwell
2007-11-21 3:42 ` Stephen Rothwell
2007-11-21 3:49 ` Stephen Rothwell
2007-11-27 22:57 ` Arnd Bergmann
2007-11-21 4:45 ` Kumar Gala [this message]
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=53FD3FB3-960E-48B8-8FF3-8233FDCD5B61@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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