linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: dhowells@redhat.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	linux@arm.linux.org.uk, starvik@axis.com,
	jesper.nilsson@axis.com, ysato@users.sourceforge.jp,
	takata@linux-m32r.org, geert@linux-m68k.org,
	zippel@linux-m68k.org, gerg@uclinux.org, ralf@linux-mips.org,
	benh@kernel.crashing.org, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, lethal@linux-sh.org,
	davem@davemloft.net, jdike@addtoit.com, tglx@linutronix.de,
	mingo@redhat.com, hpa@zytor.com, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 3/3] generic sys_ipc wrapper
Date: Wed, 06 Jan 2010 19:16:12 +0000	[thread overview]
Message-ID: <7501.1262805372@redhat.com> (raw)
In-Reply-To: <20100106172152.GC17163@lst.de>

Christoph Hellwig <hch@lst.de> wrote:

> various architectures have different strategies for the SHMAT version 1 case
> which apparently never gets used - at least on i386 it seems superflous as
> the compat code on x86-64 and ia64 doesn't even bother to implement it.

The SHMAT version 1 case can be dropped for FRV and MN10300 - neither of them
support iBCS.

> frv goes even further and uses unsigned long for all parameters execept for
> "ptr" which is a pointer type everywhere.  The change from int to unsigned
> long for "third" and back to "int" for the others on frv should be fine due
> to the in-register calling conventions for syscalls (we already had a
> similar issue with the generic sys_ptrace), but I'd prefer to have the arch
> maintainers looks over this in details.

That should be okay - the registers are all 32-bits, so int, long and pointers
are all the same size.

David

  parent reply	other threads:[~2010-01-06 19:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 17:21 [PATCH 3/3] generic sys_ipc wrapper Christoph Hellwig
2010-01-06 17:21 ` Christoph Hellwig
2010-01-06 18:22 ` Al Viro
2010-01-06 19:16 ` David Howells [this message]
2010-01-06 19:52 ` Arnd Bergmann
2010-01-06 19:59   ` Russell King - ARM Linux
2010-01-06 19:59     ` Russell King - ARM Linux
2010-01-06 20:48     ` Arnd Bergmann
2010-01-06 22:33 ` Heiko Carstens
2010-01-08  9:50 ` [PATCH v2 " Christoph Hellwig
2010-01-08 10:03   ` [PATCH v3 " Christoph Hellwig
2010-01-08 10:57     ` Arnd Bergmann
2010-01-08 15:34       ` Christoph Hellwig
2010-01-08 15:49         ` Arnd Bergmann
2010-01-10  4:51     ` Al Viro
2010-01-14 15:25   ` David Howells

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=7501.1262805372@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=hch@lst.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=jdike@addtoit.com \
    --cc=jesper.nilsson@axis.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=starvik@axis.com \
    --cc=takata@linux-m32r.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ysato@users.sourceforge.jp \
    --cc=zippel@linux-m68k.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).