-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
amdgpu: add kernelModule.patches option #321663
Open
Atemu
wants to merge
3
commits into
NixOS:master
Choose a base branch
from
Atemu:amdgpu-patches
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# TODO there should probably be a generic mechanism to patch any in-kernel module like this | ||
{ | ||
stdenv, | ||
kernel, # The kernel to patch | ||
patches ? [ ], | ||
}: | ||
|
||
stdenv.mkDerivation { | ||
pname = "amdgpu-kernel-module-customised"; | ||
inherit (kernel) | ||
src | ||
version | ||
postPatch | ||
nativeBuildInputs | ||
modDirVersion | ||
; | ||
patches = kernel.patches or [ ] ++ patches; | ||
|
||
modulePath = "drivers/gpu/drm/amd/amdgpu"; | ||
|
||
buildPhase = '' | ||
BUILT_KERNEL=${kernel.dev}/lib/modules/$modDirVersion/build | ||
|
||
cp $BUILT_KERNEL/Module.symvers $BUILT_KERNEL/.config ${kernel.dev}/vmlinux ./ | ||
|
||
make "-j$NIX_BUILD_CORES" modules_prepare | ||
make "-j$NIX_BUILD_CORES" M=$modulePath modules | ||
''; | ||
|
||
installPhase = '' | ||
make \ | ||
INSTALL_MOD_PATH="$out" \ | ||
XZ="xz -T$NIX_BUILD_CORES" \ | ||
M="$modulePath" \ | ||
modules_install | ||
''; | ||
|
||
meta = { | ||
description = "AMDGPU kernel module"; | ||
inherit (kernel.meta) license; | ||
}; | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not really keen on the idea, which problems would it solve specifically for
amdgpu
module?If anything like this to be introduced, I think it should be standardised and available for all modules. Perhaps @K900 wants to take a look here as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had two issues that I needed to patch the amdgpu module for so far:
I'd also like this to be a standard option but I think that can come later. No need to perfect it in the V1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really, really don't want to be setting this precedent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I could certainly see this being a footgun, I don't really see any great danger here; could you elaborate?
I was also planning on making the unprivileged high-priority queue patch into a stand-alone option and providing some hacks in the Steam module to make the SteamVR setup experience smoother.
https://github.com/Atemu/nixos-config/blob/93b9546d1698286367bdb8826a3d827d5527128c/modules/gaming/module.nix#L116-L126
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a generic mechanism would be nice, is there any way to unstall this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on the generic mechanism.
I think a challenge here could be to make it easy to configure for users (i.e.
boot.kernelModules."amdgpu".patches = [...]
), as we would somehow need to map module names to module paths within the kernel source tree.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Building a good interface here would be hard as some modules that are conceptually one unit may be constituted of multiple individual module files.
That's at least part of the reason why I limited my work to AMDGPU first. I'd prefer if we just merged this as iteration 1 and came up with a good design for a generic mechanism in iteration 2.
I know it's hard but we need to put a limit on our perfectionism sometimes ;)
@K900 could you share your doubts about "setting this precedent"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly my concern is that we're giving users a tool that's very sharp and very easy to hold wrong, and the failure mode is not great.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, the initial goal of this, that being the capability issues, should really be fixed somewhere at a higher level (possibly in bwrap itself even?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #217119
In short:
Applications inside of user namespaces can never have effective file capabilities. This is just a design decision of the kernel. There have been numerous attempts to move away from capabilities specifically for high priority DRM contexts (which is what SteamVR needs) but none of them have made it into the kernel yet.