Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #60186
| From | Bastian Blank <waldi@debian.org> |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Revisiting x32 ABI state |
| Date | 2018-02-11 11:20 +0100 |
| Message-ID | <vhWTL-E7-3@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Moin After almost four years and due to recent changes in the syscall path, I'd like to revisit our current handling of the x32 ABI. Currently we disable support for the x32 ABI on runtime, enabling it needs a kernel command line parameter. This Debian specific change was done due to concerns of ABI specific problems with the pretty new code. In 4.15.2 the syscall path was cleaned up. The so called "fast-path" was dropped completely, it didn't provide much of a fast path anymore because of the whole Spectre and Meltdown stuff. Also our patch made inline patches of the fast path, to remove the overhead of the checks. I think after that four years we shoud revisit that change. Do we still think x32 may be a problem? Does the patch introduce runtime latency due to it's not longer inline patched form? Regards, Bastian -- There is a multi-legged creature crawling on your shoulder. -- Spock, "A Taste of Armageddon", stardate 3193.9
Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Revisiting x32 ABI state Bastian Blank <waldi@debian.org> - 2018-02-11 11:20 +0100 Re: Revisiting x32 ABI state Ben Hutchings <ben@decadent.org.uk> - 2018-02-11 23:30 +0100
csiph-web