[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65da77f7-bbd4-4cbe-a06c-75f10a6ec4ce@lunn.ch>
Date: Fri, 31 Jan 2025 17:05:03 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Christian Schrefl <chrisi.schrefl@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Jonathan Corbet <corbet@....net>,
Russell King <linux@...linux.org.uk>,
Rudraksha Gupta <guptarud@...il.com>,
Ard Biesheuvel <ardb@...nel.org>,
Geert Stappers <stappers@...ppers.nl>,
Jamie Cunliffe <Jamie.Cunliffe@....com>,
Sven Van Asbroeck <thesven73@...il.com>,
rust-for-linux@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3] arm: rust: Enable Rust support for ARMv7
> To fix this Rust would have to provide a way to build the core
> library without float support. I don't know if there is a plan
> already to allow this.
Floating point is banned within the kernel, except for in very narrow
conditions, because the floating point registers are lazy saved on
context switch. If the kernel uses the floating point registers, you
can break user space in bad ways.
I expect this has been discussed, since it is well known kernel
restriction. Maybe go see what happened to that discussion within RfL?
Andrew
Powered by blists - more mailing lists