[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3412fbc-0b32-4402-a3c8-6ccaf42a2ee4@lunn.ch>
Date: Mon, 9 Oct 2023 16:56:36 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Andrea Righi <andrea.righi@...onical.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, greg@...ah.com, tmgross@...ch.edu
Subject: Re: [PATCH net-next v3 0/3] Rust abstractions for network PHY drivers
On Mon, Oct 09, 2023 at 04:21:09PM +0200, Andrea Righi wrote:
> On Mon, Oct 09, 2023 at 02:53:00PM +0200, Miguel Ojeda wrote:
> > On Mon, Oct 9, 2023 at 2:48 PM Andrew Lunn <andrew@...n.ch> wrote:
> > >
> > > Any ideas?
> >
> > That is `RETHUNK` and `X86_KERNEL_IBT`.
> >
> > Since this will keep confusing people, I will make it a `depends on !`
> > as discussed in the past. I hope it is OK for e.g. Andrea.
>
> Disabling RETHUNK or IBT is not acceptable for a general-purpose kernel.
> If that constraint is introduced we either need to revert that patch
> in the Ubuntu kernel or disable Rust support.
>
> It would be nice to have a least something like
> CONFIG_RUST_IS_BROKEN_BUT_IM_HAPPY, off by default, and have
> `RUST_IS_BROKEN_BUT_IM_HAPPY || depends on !`.
Should this actually be CONFIG_RUST_IS_BROKEN_ON_X86_BUT_IM_HAPPY ?
At lest for networking, the code is architecture independent. For a
driver to be useful, it needs to compile for most architectures. So i
hope Rust will quickly make it to other architectures. And for PHY
drivers, ARM and MIPS are probably more important than x86.
Andrew
Powered by blists - more mailing lists