[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z8c8-q1jMDm3t-OL@kernel.org>
Date: Tue, 4 Mar 2025 19:48:42 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Fiona Behrens <me@...enk.dev>
Cc: Bart Van Assche <bvanassche@....org>,
Steven Rostedt <rostedt@...dmis.org>,
Jason Gunthorpe <jgg@...dia.com>, Kees Cook <kees@...nel.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Christoph Hellwig <hch@...radead.org>,
rust-for-linux <rust-for-linux@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>,
David Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
ksummit@...ts.linux.dev
Subject: Re: Rust kernel policy
On Tue, Mar 04, 2025 at 12:17:54PM +0100, Fiona Behrens wrote:
> I do have a new pr open in the nix repo, it still needs some polishing
> and gcc and all that. but it does work for me to build using clang and
> also run kunit.
>
> https://github.com/Rust-for-Linux/nix/pull/8
My scenario has no connection to this. Let me explain.
I needed a system comparable to BuildRoot and Yocto to build images and
manage complexity of two toolchains. I.e. I use it only as build system
not as an environment for doing kernel development.
I.e. what I created is
https://gitlab.com/jarkkojs/linux-tpmdd-nixos
which replaces eventually
https://codeberg.org/jarkko/linux-tpmdd-test
What I can do with my environment is essentially along the lines of
1. docker compose up --build
2. qemu-system-x86_64 -M pc -m 2G -drive if=pflash,format=raw,unit=0,file=output/firmware.fd -drive file=output/tpmdd-nixos.qcow2,if=virtio,format=qcow2 -nographic
I use this in Fedora Linux where I do all my kernel development. This
is something I plan to update to MAINTAINERS as a test environment.
>
> Thanks
> Fiona
>
BR, Jarkko
Powered by blists - more mailing lists