chore(zone): reduce linux config - #239
Draft
alexandermerritt wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Alexander M. Merritt <alexander@edera.dev>
Contributor
Author
|
Kernel finished building for me on a 32-core EPYC machine with no caching: |
Contributor
Author
|
I want to try this kernel out with the e2e tests somehow before we merge in. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our current fragment is quite small.
What that means: default-enabled config options in Kconfig that are not explicitly disabled in our fragment, will be enabled once merged with a defconfig for the architecture. Examples include wireless hardware support and networking, bluetooth, sound, etc. which we all do not need for zone kernels.
Goals: reduce the amount of text in the kernel, second to reduce build times.
This is one of many in the future to come; we'll need to
is not setany default-enabled configuration options we do not want. For future kernels, we'll need to check for any newly introduce configuration options that are default-enabled and repeat for them.I'd like to properly generate the fragment rather than have us go with manually editing the config when we want to tweak something.