zenergy: init at 0-unstable-2024-05-19

[wizardlink]

Description of changes

Adds a new kernel module, zenergy, this is necessary for accessing CPU power draw data without root permission, specifically MangoHud requires it to be able to show the user their CPU power draw.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[wizardlink]

I apologize if I missed something in advance, first time contributing to the repository! I am a little confused though with the testing and release note markdown, for the testing I couldn't find an example of a kernel module being tested, if it's even possible with the suite available; whereas the markdown file, it implies that not all additions will be covered, so would this PR be applicable still? Not quite sure.

[SuperSandro2000]

It should be enough to set makeTarget and makeFlags like already done

[wizardlink]

I searched in the repository for examples and tried to replicate, but in the installPhase the KDIR environment wasn't set on top of not running modules_install with makeTargets = [ "modules_install" ].

Am I missing something?

[wizardlink]

@SuperSandro2000 can you also give me an update on this?

[SuperSandro2000]

I am a little confused though with the testing and release note markdown, for the testing I couldn't find an example of a kernel module being tested, if it's even possible with the suite available; whereas the markdown file, it implies that not all additions will be covered, so would this PR be applicable still? Not quite sure.

If you are doing the change on top of nixos-unstable, you can just rebuild your system with it and try to use the kernel module like normally done.
We don't need a release note entry here.

[wizardlink]

I've been using that kernel module locally since the PR has been open, so I can attest that it's in working condition!

I'll be adjusting for the review ASAP. o7