From: David Woodhouse <dwmw2@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mauelshagen@sistina.com, linux-kernel@vger.kernel.org,
mge@sistina.com, hch@caldera.de
Subject: Re: LVM 1.0 release decision
Date: Sun, 13 May 2001 18:36:11 +0100 [thread overview]
Message-ID: <23605.989775371@redhat.com> (raw)
In-Reply-To: <15100.37367.477922.66043@pizda.ninka.net>
In-Reply-To: <15100.37367.477922.66043@pizda.ninka.net> <20010511162745.B18341@sistina.com> <E14yDyI-0000yE-00@the-village.bc.nu> <20010511171124.M30355@athlon.random> <15100.18375.367656.3591@pizda.ninka.net> <20010512032453.A8259@athlon.random>
davem@redhat.com said:
> Andrea Arcangeli writes:
> > Related side note: for the x86-64 kernel we won't support the emulation
> > of the lvm ioctl from the 32bit executables to avoid the pointer
> > conversion an mainteinance pain enterely, at least in the early stage
> > the x86-64 lvmtools will have to be compiled elf64.
> I think that's a bad decision, but it is your's.
> To me, either you support fully the 32-bit execution environment or
> you do not. After all the work that myself and others have done for
> other platforms, there really is no need to cut corners in this area.
IMHO, no 64-bit architecture code should provide translation functions for
ioctls from 32-bit binaries.
This is now a sufficiently common requirement that it shouldn't be repeated
by all architectures that require it - it should be somewhere common.
Like linux/abi/ioctl32/
--
dwmw2
next prev parent reply other threads:[~2001-05-13 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 16:27 LVM 1.0 release decision Heinz J. Mauelshagen
2001-05-11 14:32 ` Alan Cox
2001-05-11 15:11 ` Andrea Arcangeli
2001-05-11 20:12 ` David S. Miller
2001-05-12 1:24 ` Andrea Arcangeli
2001-05-12 1:29 ` David S. Miller
2001-05-12 2:54 ` Andrea Arcangeli
2001-05-12 5:19 ` David S. Miller
2001-05-12 13:39 ` Andrea Arcangeli
2001-05-13 17:36 ` David Woodhouse [this message]
2001-05-13 18:39 ` Alan Cox
2001-05-13 23:17 ` Chris Wedgwood
2001-05-13 19:25 ` Christoph Hellwig
2001-05-11 15:42 ` H. Peter Anvin
2001-05-11 17:02 ` Andreas Dilger
2001-05-16 15:03 ` Heinz J. Mauelshagen
2001-05-16 23:38 ` Alan Cox
2001-05-11 14:39 ` Jeff Garzik
2001-05-11 14:48 ` Mark Hahn
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=23605.989775371@redhat.com \
--to=dwmw2@infradead.org \
--cc=Mauelshagen@sistina.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mge@sistina.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 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.