diff options
author | David Gow <davidgow@google.com> | 2024-06-05 06:40:50 +0800 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2024-07-03 12:22:22 +0200 |
commit | ab0f4cedc3554f921691ce5b63d59e258154e799 (patch) | |
tree | fd0cc6080f8c456a3646207d65046c05f69fae59 /io_uring | |
parent | 9a2123b397bbe0da5e853273369d63779ac97c8c (diff) | |
download | linux-stable-ab0f4cedc3554f921691ce5b63d59e258154e799.tar.gz linux-stable-ab0f4cedc3554f921691ce5b63d59e258154e799.tar.bz2 linux-stable-ab0f4cedc3554f921691ce5b63d59e258154e799.zip |
arch: um: rust: Add i386 support for Rust
At present, Rust in the kernel only supports 64-bit x86, so UML has
followed suit. However, it's significantly easier to support 32-bit i386
on UML than on bare metal, as UML does not use the -mregparm option
(which alters the ABI), which is not yet supported by rustc[1].
Add support for CONFIG_RUST on um/i386, by adding a new target config to
generate_rust_target, and replacing various checks on CONFIG_X86_64 to
also support CONFIG_X86_32.
We still use generate_rust_target, rather than a built-in rustc target,
in order to match x86_64, provide a future place for -mregparm, and more
easily disable floating point instructions.
With these changes, the KUnit tests pass with:
kunit.py run --make_options LLVM=1 --kconfig_add CONFIG_RUST=y
--kconfig_add CONFIG_64BIT=n --kconfig_add CONFIG_FORTIFY_SOURCE=n
An earlier version of these changes was proposed on the Rust-for-Linux
github[2].
[1]: https://github.com/rust-lang/rust/issues/116972
[2]: https://github.com/Rust-for-Linux/linux/pull/966
Signed-off-by: David Gow <davidgow@google.com>
Link: https://patch.msgid.link/20240604224052.3138504-1-davidgow@google.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'io_uring')
0 files changed, 0 insertions, 0 deletions