[Kernel CI] Refactor config.sh & Fix for New Graysky Compiler Patch
#102
Conversation
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
(We don't release .config though)
Locietta
force-pushed
the
config-arch
branch
from
66fb420 to
ddd1bca
Compare
mistakenly remove it
|
EDIT: see softprops/action-gh-release#556 |
Locietta
force-pushed
the
config-arch
branch
from
6adebaf to
b2ca290
Compare
Locietta
force-pushed
the
config-arch
branch
from
b2ca290 to
e7dbc93
Compare
Locietta
added a commit
that referenced
this pull request
Dec 19, 2024
#102 remove IS_LTS env in *.yml, but not change build.sh accordingly, which makes build.sh always selects to non-ccache branch. Add option parser like that in setup.sh and modify *.yml, which should fix ccache. Also remove old SMT detection code. `nproc` itself already respects SMT. Like with 8C,16T processor, `nproc` will return 16. `nproc --all` basically is same as `nproc` but it will ignore cgroup limitation forced by containers like docker, and also on motherboards supporting hotplug cpus it will return max possible cpu slots instead of the number of installed count. So yeah, sometimes `nproc --all` returns a bigger number than `nproc`, but those "extra" cpus aren't actually available for use. So let's just use `nproc`. But use 2*nproc might still make sense if compilation is actually IO-bounded. I tested nproc vs 2*nproc on my private repo's action. It seems like no noticable difference though. Maybe we should revisit the thread count decision someday later. (cherry picked from commit f05d3d5c422738ad90237753b9bd60396ded6238)
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.
Xanmod 6.12 picks the updated Graysky compiler patch, which uses
CONFIG_X86_64_VERSIONandCONFIG_X86_64_VERSION=<level>to specify the x86_64 psABI level. This requires a workaround to handle properly. Given the increased complexity of the CI logic, I've consolidated everything intoconfig.shinstead of spreading it acrossbuild.ymlandbuild-lts.yml. This should make maintenance more straightforward.I've noticed that
make savedefconfigon newer kernel version will remove more config, which causes some configs dropped on LTS (i.e. some configs can be inferred on 6.12 but not 6.6). Sharing a singledefconfigbetween LTS and MAIN kernels is error-prone, so I’ve opted to split them.I’ve also moved the kernel source download logic into
config.sh. Given that the script now handles more than just config, I’ve renamed it tosetup.shfor clarity.