From: Rich Felker <dalias@libc.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: tg@mirbsd.de, Linus Torvalds <torvalds@linux-foundation.org>,
X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Florian Weimer <fweimer@redhat.com>,
Mike Frysinger <vapier@gentoo.org>,
"H. J. Lu" <hjl.tools@gmail.com>,
x32@buildd.debian.org, Arnd Bergmann <arnd@arndb.de>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: Can we drop upstream Linux x32 support?
Date: Tue, 11 Dec 2018 18:38:05 -0500 [thread overview]
Message-ID: <20181211233805.GO23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <CALCETrWgpAX7FV23zHmid83SsgnwFMKD4a_-xSEgB6v0kJR5sA@mail.gmail.com>
On Tue, Dec 11, 2018 at 03:22:43PM -0800, Andy Lutomirski wrote:
> On Tue, Dec 11, 2018 at 2:14 PM Thorsten Glaser <tg@mirbsd.de> wrote:
> > I was also considering investing a nontrivial amount of
> > work into porting klibc to x32, since hpa does not wish
> > to do it himself. Thankfully I have only done a bit yet.
> >
> > Furthermore, x32 was the first of the many *64ilp32
> > architectures; I know I’ve seen amd64ilp32 and at least
> > one other I don’t recall. It will have prototyped many
> > of the problems users of these will run in, and I’d prefer
> > to keep it (completely selfish because I don’t wish to
> > have to crossgrade a whole system yet again).
>
> it kind of seems like arm64's lesson is "don't do it like x32".
>
> There's some effort going on right now to make it possible to add
> syscalls without having to muck with every single architecture. I
> don't really want x32 to derail that effort. I suppose we could say
> that x32 stays but that it simply gets no new syscalls, but that seems
> a bit lame. Unfortunately, on x86, x32 really is a third ABI that is
> not compatible in a structure-memory-layout sense with the other two.
> What happens if someone adds a struct like:
>
> struct nasty_on_x32 {
> __kernel_long_t a;
> void * __user b;
> };
>
> On x86_64, that's two 8-byte fields. On x86_32, it's two four-byte
> fields. On x32, it's an 8-byte field and a 4-byte field. Now what?
>
> I'm sure we could have some magic gcc plugin or other nifty tool that gives us:
>
> copy_from_user(struct struct_name, kernel_ptr, user_ptr);
>
> where it automatically generates code for all possible ABIs to copy
> over the struct and dispatches dynamically based on the current
> syscall ABI, but I have trouble imagining anyone volunteering to
> actually do this work. Instead we get ad hoc fixes for each syscall,
> along the lines of preadv64v2(), which get done when somebody notices
> a problem.
For what it's worth, this is exactly what I plan to do if/when I ever
get to doing my kernel with multiple/universal userspace ABI support:
pure-data markup for the data structures (and syscall argument
arrangements) userspace is speaking, with generic marshalling code.
But I don't think it's easy to retrofit to Linux, and probably
wouldn't be welcome there.
Rich
next prev parent reply other threads:[~2018-12-11 23:38 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 1:23 Andy Lutomirski
2018-12-11 1:40 ` Linus Torvalds
2018-12-11 2:22 ` hpa
2018-12-11 8:16 ` Florian Weimer
2018-12-11 21:53 ` Thorsten Glaser
2018-12-11 23:22 ` Andy Lutomirski
2018-12-11 23:35 ` Thorsten Glaser
2018-12-11 23:55 ` Arnd Bergmann
2018-12-12 2:24 ` Andy Lutomirski
2018-12-12 2:33 ` Thorsten Glaser
2018-12-12 9:04 ` Arnd Bergmann
2018-12-12 18:14 ` Joseph Myers
2018-12-12 18:50 ` Ivan Ivanov
2018-12-12 19:12 ` Andy Lutomirski
2018-12-12 19:18 ` Ivan Ivanov
2018-12-12 16:39 ` Andy Lutomirski
2018-12-12 16:52 ` Rich Felker
2018-12-12 18:03 ` Andy Lutomirski
2018-12-13 12:40 ` Catalin Marinas
2018-12-13 15:57 ` Rich Felker
2018-12-13 16:04 ` Florian Weimer
2018-12-13 16:28 ` Rich Felker
2018-12-14 11:42 ` Florian Weimer
2018-12-14 16:13 ` Rich Felker
2018-12-13 18:42 ` Joseph Myers
2018-12-15 4:53 ` Thorsten Glaser
2018-12-11 23:38 ` Rich Felker [this message]
2018-12-11 23:40 ` Maciej W. Rozycki
2018-12-13 14:38 ` Olof Johansson
2018-12-13 15:46 ` Lance Richardson
2018-12-13 16:11 ` Richard Purdie
2018-12-11 3:14 ` H.J. Lu
2018-12-11 5:35 ` Andy Lutomirski
2018-12-11 9:02 ` Arnd Bergmann
2018-12-11 11:32 ` Catalin Marinas
2018-12-11 11:37 ` Florian Weimer
2018-12-11 11:52 ` Catalin Marinas
2018-12-11 5:46 ` Christian Brauner
2018-12-11 10:29 ` John Paul Adrian Glaubitz
2018-12-11 10:37 ` Florian Weimer
2018-12-11 10:44 ` John Paul Adrian Glaubitz
2018-12-11 21:59 ` Thorsten Glaser
2018-12-11 23:33 ` Rich Felker
2018-12-13 5:03 ` Kevin Easton
2018-12-13 9:05 ` Richard Weinberger
2018-12-13 9:37 ` Sven Hartrumpf
2018-12-13 9:57 ` Adam Borowski
2018-12-13 18:50 ` Sven Hartrumpf
2018-12-13 12:12 ` Kevin Easton
2018-12-14 14:38 ` David Laight
2018-12-14 15:17 ` Richard Weinberger
2018-12-13 16:02 ` Rich Felker
2018-12-14 14:13 ` Bernd Petrovitsch
2018-12-14 16:17 ` Rich Felker
2018-12-14 16:29 ` Bernd Petrovitsch
2018-12-14 16:38 ` Florian Weimer
2018-12-14 16:55 ` Rich Felker
2018-12-14 18:58 ` Andy Lutomirski
2018-12-14 19:59 ` Lance Richardson
2018-12-14 20:13 ` Linus Torvalds
2018-12-14 21:27 ` Andy Lutomirski
2018-12-14 21:16 ` Thomas Schöbel-Theuer
2018-12-14 21:24 ` Andy Lutomirski
2018-12-14 21:41 ` Thomas Schöbel-Theuer
2018-12-15 7:41 ` Thomas Schoebel-Theuer
2018-12-15 15:30 ` Andy Lutomirski
2019-01-09 12:41 ` Florian Weimer
2019-01-09 16:02 ` Rich Felker
2019-01-22 13:34 ` Enrico Weigelt, metux IT consult
2018-12-11 20:38 Shawn Rutledge
2018-12-12 0:00 ` Maciej W. Rozycki
2018-12-12 9:12 Steven Newbury
2018-12-12 10:48 ` Thorsten Glaser
2018-12-12 13:27 ` Steven Newbury
2018-12-12 14:01 ` Rich Felker
2018-12-12 14:46 ` Steven Newbury
2018-12-12 16:05 ` Rich Felker
2018-12-13 16:17 tedheadster
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=20181211233805.GO23599@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tg@mirbsd.de \
--cc=torvalds@linux-foundation.org \
--cc=vapier@gentoo.org \
--cc=will.deacon@arm.com \
--cc=x32@buildd.debian.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®