All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, kraxel@redhat.com, arnd@arndb.de,
	linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
	mingo@elte.hu, ralf@linux-mips.org, tglx@linutronix.de,
	viro@zeniv.linux.org.uk
Subject: Re: + preadv-pwritev-add-preadv-and-pwritev-system-calls.patch added to -mm tree
Date: Mon, 02 Feb 2009 13:51:27 -0800	[thread overview]
Message-ID: <49876ADF.80201@zytor.com> (raw)
In-Reply-To: <200902022135.n12LZa1a010673@imap1.linux-foundation.org>

> 
> This prototype has one problem though: On 32bit archs is the (64bit)
> offset argument unaligned, which the syscall ABI of several archs doesn't
> allow to do.  At least s390 needs a wrapper in glibc to handle this.  As
> we'll need a wrappers in glibc anyway I've decided to push problem to
> glibc entriely and use a syscall prototype which works without
> arch-specific wrappers inside the kernel: The offset argument is
> explicitly splitted into two 32bit values.
> 

This is also an excellent example of why having syscall stubs 
autogenerated would be a very good thing, to avoid these kinds of 
abortions polluting the ABIs of *every* architecture...

	-hpa

  parent reply	other threads:[~2009-02-02 21:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 21:35 + preadv-pwritev-add-preadv-and-pwritev-system-calls.patch added to -mm tree akpm
     [not found] ` <200902022135.n12LZa1a010673-AB4EexQrvXRQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2009-02-02 21:50   ` H. Peter Anvin
2009-02-02 21:50     ` H. Peter Anvin
     [not found]     ` <49876A91.4000705-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2009-02-03 10:14       ` Gerd Hoffmann
2009-02-03 10:14         ` Gerd Hoffmann
     [not found]         ` <49881904.30705-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-02-03 17:06           ` H. Peter Anvin
2009-02-03 17:06             ` H. Peter Anvin
     [not found]             ` <498879B3.8030002-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2009-02-03 17:15               ` Russell King
2009-02-03 17:15                 ` Russell King
2009-02-03 17:29                 ` H. Peter Anvin
     [not found]                 ` <20090203171559.GA20898-f404yB8NqCZvn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2009-02-03 17:29                   ` H. Peter Anvin
2009-02-03 17:29                     ` H. Peter Anvin
     [not found]                     ` <49887EF4.1090300-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2009-02-03 17:42                       ` Russell King
2009-02-03 17:42                         ` Russell King
2009-02-03 20:19                         ` H. Peter Anvin
2009-02-03 20:19                           ` H. Peter Anvin
2009-02-05  0:42                         ` H. Peter Anvin
2009-02-05  0:42                           ` H. Peter Anvin
2009-02-02 21:51 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-02 21:35 akpm

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=49876ADF.80201@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=kraxel@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mm-commits@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.