public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andi Kleen <ak@suse.de>,
	davem@davemloft.net, matthew@wil.cx, hch@lst.de, akpm@osdl.org,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH, for review 1/3] compat_sys_{read,write}
Date: Fri, 01 Jul 2005 08:58:25 +0100	[thread overview]
Message-ID: <9482.1120204705@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20050701145642.6a3d6542.sfr@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> This patch introduces compatibility syscalls for read and write and the
> equivalent hooks in struct file_operations.  These are neede to support
> the badly designed (i.e. broken) input layer evdev read and write
> interfaces.

Should this also extend to the pread/pwrite syscalls?

> +asmlinkage ssize_t sys_write(unsigned int fd, const char __user * buf,
> +		size_t count)
> +{
> +	return do_sys_write(fd, buf, count, 0);
> +}

I think my biggest objection to this is that it'll stick another "frame" on
the stack. For something like this the compiler probably can't tail-call, at
least not on archs like i386 where the extra argument is passed on the stack.
For an arch that passes at least the first four arguments in registers, it
probably can, but I don't know that it will. Have you waved this in front of
any compiler hackers?

David

  parent reply	other threads:[~2005-07-01  7:58 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28  7:27 input compat stuff Christoph Hellwig
2005-06-28  8:14 ` RFC: is_compat_task (Was: Re: input compat stuff) Stephen Rothwell
2005-06-28  8:30   ` RFC: is_compat_task David S. Miller
2005-06-28  9:17   ` RFC: is_compat_task (Was: Re: input compat stuff) Andi Kleen
2005-06-28  9:23     ` RFC: is_compat_task David S. Miller
2005-06-28  9:27       ` Andi Kleen
2005-06-28  9:29         ` David S. Miller
2005-06-28  9:33           ` Andi Kleen
2005-06-28 11:18     ` RFC: is_compat_task (Was: Re: input compat stuff) Matthew Wilcox
2005-06-28 12:05       ` Andi Kleen
2005-06-28 20:47       ` RFC: is_compat_task David S. Miller
2005-06-29  6:41         ` Stephen Rothwell
2005-06-29 11:01           ` Arnd Bergmann
2005-06-29 12:12           ` Andi Kleen
2005-06-30  7:57             ` Stephen Rothwell
2005-06-30  8:42               ` Andi Kleen
2005-06-30 14:38                 ` Stephen Rothwell
2005-06-30 15:28                   ` Stephen Rothwell
2005-06-30 15:49                     ` Andi Kleen
2005-06-30 23:29                       ` Paul Mackerras
2005-07-01  2:34                         ` David S. Miller
2005-07-01 13:48                         ` Andi Kleen
2005-07-04  3:36                           ` Paul Mackerras
2005-07-04 23:02                             ` David S. Miller
2005-07-01  4:56                       ` [PATCH, for review 1/3] compat_sys_{read,write} Stephen Rothwell
2005-07-01  4:58                         ` [PATCH, for review 2/3] hook up compat_sys_{read,write} syscalls Stephen Rothwell
2005-07-01  5:01                         ` [PATCH, for review 3/3] fix evdev Stephen Rothwell
2005-07-01  7:58                         ` David Howells [this message]
2005-07-01  8:24                           ` [PATCH, for review 1/3] compat_sys_{read,write} Stephen Rothwell
2005-07-21  7:05                         ` Stephen Rothwell
2005-07-21  8:05                           ` David S. Miller
2005-07-21  8:28                             ` Stephen Rothwell
2005-06-29 10:36         ` RFC: is_compat_task Andi Kleen
2005-06-28 16:09     ` RFC: is_compat_task (Was: Re: input compat stuff) Stephen Rothwell
2005-06-28 16:14       ` Andi Kleen
2005-06-28 16:34         ` Stephen Rothwell
2005-06-28 16:44           ` Andi Kleen
2005-06-30 10:16     ` Ralf Baechle
2005-06-28  9:16 ` input compat stuff Andi Kleen

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=9482.1120204705@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=hch@lst.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=sfr@canb.auug.org.au \
    /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