This is my new testing tree for my kernel tree. It will over time replace
my previous BuildRoot based testing tree (but not just yet).

Depending on host `docker compose up --build` (or podman) will spit out
rootfs and OVMF/AAVMF image depending on host where it is compiled.

This allows a few new perks such as:

1. Trivial Aarch64 testing in QEMU and in macOS (without requiring dual
   boot to Asahi Linux necessarily).
2. Testing of more complex configurations such as Integrity Measurement
   Architecture (IMA).
3. Easier management of both GCC and Rust toolchains, thus enabling
   testing of Rust-enabled kernel.

Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 8e0736dc2ee0..ea7c40b76181 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -24033,6 +24033,7 @@ R:	Jason Gunthorpe <jgg@ziepe.ca>
 L:	linux-integrity@vger.kernel.org
 S:	Maintained
 W:	https://codeberg.org/jarkko/linux-tpmdd-test
+W:	https://gitlab.com/jarkkojs/linux-tpmdd-nixos
 Q:	https://patchwork.kernel.org/project/linux-integrity/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
 F:	Documentation/devicetree/bindings/tpm/
-- 
2.48.1

On Thu, Mar 6, 2025 at 10:17 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
>
> This is my new testing tree for my kernel tree. It will over time replace
> my previous BuildRoot based testing tree (but not just yet).

Thanks for Cc'ing! I assume this is related to your subsystem and that
it will go through there.

Cc'ing Fiona as well since she was interested in Nix and Tamir who
does macOS; so they may be interested.

Cheers,
Miguel

On Fri, Mar 07, 2025 at 10:22:10AM +0100, Miguel Ojeda wrote:
> On Thu, Mar 6, 2025 at 10:17 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > This is my new testing tree for my kernel tree. It will over time replace
> > my previous BuildRoot based testing tree (but not just yet).
> 
> Thanks for Cc'ing! I assume this is related to your subsystem and that
> it will go through there.
> 
> Cc'ing Fiona as well since she was interested in Nix and Tamir who
> does macOS; so they may be interested.

Yeah, so I just used get_maintainer.pl and it picked you but I'm
happy if you enjoy it :-) linux-tpmdd comes originally from TPM driver
but these days it's really just my maintainer tree for every possible
pull request I do, as I'm also e.g. Linux keyring co-maintainer.

My biggest barrier with Rust has been testing (like almost always in any
software engineering problem) so I just figured out something that would
sort it out for me. I also thought that by starting doing some testing
for Rust patch sets that contain some tests would be a low-barrier way
for me to learn a bit how everything works in that side.

I think I quickly talked about this with Fiona and this is a bit
different angle in a way i.e., using Nix for profit as a tool to
implement together with Docker a trivial embedded build system so that
you can build kernel + EFI in any operating system (I personally use
Fedora).

> 
> Cheers,
> Miguel

BR, Jarkko

Jarkko Sakkinen <jarkko@kernel.org> writes:

> On Fri, Mar 07, 2025 at 10:22:10AM +0100, Miguel Ojeda wrote:
>> On Thu, Mar 6, 2025 at 10:17 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
>> >
>> > This is my new testing tree for my kernel tree. It will over time replace
>> > my previous BuildRoot based testing tree (but not just yet).
>> 
>> Thanks for Cc'ing! I assume this is related to your subsystem and that
>> it will go through there.
>> 
>> Cc'ing Fiona as well since she was interested in Nix and Tamir who
>> does macOS; so they may be interested.
>
> Yeah, so I just used get_maintainer.pl and it picked you but I'm
> happy if you enjoy it :-) linux-tpmdd comes originally from TPM driver
> but these days it's really just my maintainer tree for every possible
> pull request I do, as I'm also e.g. Linux keyring co-maintainer.
>
> My biggest barrier with Rust has been testing (like almost always in any
> software engineering problem) so I just figured out something that would
> sort it out for me. I also thought that by starting doing some testing
> for Rust patch sets that contain some tests would be a low-barrier way
> for me to learn a bit how everything works in that side.
>
> I think I quickly talked about this with Fiona and this is a bit
> different angle in a way i.e., using Nix for profit as a tool to
> implement together with Docker a trivial embedded build system so that
> you can build kernel + EFI in any operating system (I personally use
> Fedora).

Yeah exactly, took me a while to understand your usage :)
I use nix mainly as a dev shell and plan to add building the kernel
through nix.

Once I have the time and remember this still then I might try to include
your work in the nix repo I maintain. Maybe we can also build docker
container images for kernel development processes using nix and stuff
like that.

Thanks,
Fiona

>
>> 
>> Cheers,
>> Miguel
>
> BR, Jarkko

On Thu, Mar 13, 2025 at 12:26:47PM +0100, Fiona Behrens wrote:
> Jarkko Sakkinen <jarkko@kernel.org> writes:
> 
> > On Fri, Mar 07, 2025 at 10:22:10AM +0100, Miguel Ojeda wrote:
> >> On Thu, Mar 6, 2025 at 10:17 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >> >
> >> > This is my new testing tree for my kernel tree. It will over time replace
> >> > my previous BuildRoot based testing tree (but not just yet).
> >> 
> >> Thanks for Cc'ing! I assume this is related to your subsystem and that
> >> it will go through there.
> >> 
> >> Cc'ing Fiona as well since she was interested in Nix and Tamir who
> >> does macOS; so they may be interested.
> >
> > Yeah, so I just used get_maintainer.pl and it picked you but I'm
> > happy if you enjoy it :-) linux-tpmdd comes originally from TPM driver
> > but these days it's really just my maintainer tree for every possible
> > pull request I do, as I'm also e.g. Linux keyring co-maintainer.
> >
> > My biggest barrier with Rust has been testing (like almost always in any
> > software engineering problem) so I just figured out something that would
> > sort it out for me. I also thought that by starting doing some testing
> > for Rust patch sets that contain some tests would be a low-barrier way
> > for me to learn a bit how everything works in that side.
> >
> > I think I quickly talked about this with Fiona and this is a bit
> > different angle in a way i.e., using Nix for profit as a tool to
> > implement together with Docker a trivial embedded build system so that
> > you can build kernel + EFI in any operating system (I personally use
> > Fedora).
> 
> Yeah exactly, took me a while to understand your usage :)
> I use nix mainly as a dev shell and plan to add building the kernel
> through nix.
> 
> Once I have the time and remember this still then I might try to include
> your work in the nix repo I maintain. Maybe we can also build docker
> container images for kernel development processes using nix and stuff
> like that.

Yes, so no plans to step on your toes. I'm going to keep this
"opionated repository" for my own maintainer work :-) And
possibly for some contributions outside my usual sandbox.

That said, anything can be taken for more generic use... [ping
me for license incompatibility issues, I de-facto to GPLv3 but
permit to other licensing framework on request].

> 
> Thanks,
> Fiona

BR, Jarkko

On Thu, Mar 06, 2025 at 11:17:16PM +0200, Jarkko Sakkinen wrote:
> This is my new testing tree for my kernel tree. It will over time replace
> my previous BuildRoot based testing tree (but not just yet).
> 
> Depending on host `docker compose up --build` (or podman) will spit out
> rootfs and OVMF/AAVMF image depending on host where it is compiled.

Oops "depending on host" x2. As far as I'm concerned don't care ;-)

BR, Jarkko