public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	torvalds@transmeta.com, ak@suse.de, davem@redhat.com
Subject: Re: ioctl32 consolidation
Date: Fri, 21 Feb 2003 12:58:05 +0100	[thread overview]
Message-ID: <20030221115805.GA6445@wotan.suse.de> (raw)
In-Reply-To: <20030221113428.GF24049@atrey.karlin.mff.cuni.cz>

On Fri, Feb 21, 2003 at 12:34:29PM +0100, Pavel Machek wrote:
> Hi!
> 
> 
> > > Currently, 32-bit emulation in kernel has *5* copies, and its >1000
> > > lines each.
> > 
> > Yes :/  Consolidating all these copies into a single layer has been a
> > "project to be" for quite some time.
> > 
> > I do not know if it is too late in 2.5.x to begin this work, however.
> > We _are_ in a feature freeze...  I suppose it is up to the consensus of
> > arch maintainers, because it [obviously] does not affect ia32.
> 
> Actually Andi asked me to do the work. Dave, is it okay with you? What
> about other maintainers?

One issue you need to be careful about is that long long has different
alignment between 32bit and 64bit on ia64 and x86-64. On sparc64/mips64/ppc64
etc. that isn't the case. The x86-64 handlers convert sometimes more than
the later ones because of that.

Also some ioctl handlers are endian dependent, at least in x86-64 (I think
I commented them all). Not sure if Dave did the same.

First step probably is to just get register_ioctl32_translation into
a common header and implementation file.

-Andi

  reply	other threads:[~2003-02-21 11:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 22:31 ioctl32 consolidation Pavel Machek
2003-02-20 22:44 ` Jeff Garzik
2003-02-21 11:34   ` Pavel Machek
2003-02-21 11:58     ` Andi Kleen [this message]
2003-02-21 23:21     ` David S. Miller
2003-03-01 19:49     ` Anton Blanchard
2003-02-20 22:56 ` Max Krasnyansky
2003-02-20 23:10   ` Jeff Garzik
2003-02-21  0:36   ` David S. Miller
2003-02-21  1:31     ` Max Krasnyansky
2003-02-21  1:40       ` Jeff Garzik
2003-02-21  3:20       ` David S. Miller
     [not found] <20030221114011$5b98@gated-at.bofh.it>
     [not found] ` <20030221114011$7728@gated-at.bofh.it>
     [not found]   ` <20030221114011$25df@gated-at.bofh.it>
2003-02-21 22:27     ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2003-02-24 10:05 Martin Schwidefsky

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=20030221115805.GA6445@wotan.suse.de \
    --to=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=torvalds@transmeta.com \
    /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