Skip to contentSkip to conversation

MAINTAINERS: TPM DEVICE DRIVER: linux-tpmdd-nixos

PATCH In review Jarkko Sakkinen 3 participants 6 messages Mar 6, 2025 – Mar 14, 2025 Rust

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: TPM DEVICE DRIVER: linux-tpmdd-nixos

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.

---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)
MAINTAINERS +1 -0
index 8e0736dc2ee0..ea7c40b76181 100644
@@ -24033,6 +24033,7 @@ R:	Jason Gunthorpe <[email protected]>
 L:	[email protected]
 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/
Signature · 1 line
2.48.1
#1 lore raw
Quoted 5 lines · Jarkko Sakkinen

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

#2 lore raw
In reply to Jarkko Sakkinen
Quoted 3 lines · Jarkko Sakkinen

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

#3 lore raw
Quoted 10 lines · Miguel Ojeda
Quoted 3 lines · Jarkko Sakkinen

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).

Quoted 3 lines

Cheers,
Miguel

BR, Jarkko

#4 lore raw
Quoted 23 lines · Jarkko Sakkinen
Quoted 10 lines · Miguel Ojeda
Quoted 3 lines · Jarkko Sakkinen

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.

Quoted 5 lines

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

Quoted 6 lines
Quoted 4 lines

Cheers,
Miguel

BR, Jarkko

#5 lore raw
Quoted 31 lines · Fiona Behrens
Quoted 23 lines · Jarkko Sakkinen
Quoted 10 lines · Miguel Ojeda
Quoted 3 lines · Jarkko Sakkinen

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.

Quoted 5 lines

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).

Quoted 8 lines

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].

Quoted 3 lines

Thanks,
Fiona

BR, Jarkko