extended repo LVBS kernel

[ddstreet]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

This is early work to build a kernel in the extended repo that includes LVBS support.

Note that the accumulated LVBS patches will be rolled into a dedicated LVBS kernel tarball, instead of carrying them as individual patches like this PR. Please ignore the actual content of the LVBS patches, as that content will be reviewed/managed by a kernel git branch (and this PR shouldn't be merged until that is complete and this is updated to use the resulting LVBS kernel tarball); this PR is intended only for review of the spec file (and related) changes.

Change Log

Add spec file, etc. to enable building LVBS kernel in extended repo

Does this affect the toolchain?

NO

Test Methodology

WIP, no testing/validation yet

[reubeno]

Great to see the start of this, @ddstreet! I know we're mutually interested in seeing an LVBS-enabled kernel make its way into the extended repo.

Let us know when you're ready to start getting any early reviews/feedback on the PR. (I see it currently marked as WIP and draft.) I'm assuming @rlmenge, among others, will be keenly interested and have good suggestions.

[rlmenge]

Just checking but will this work since the lvbs_normal and lvbs_secure directories have not been created yet?

[ddstreet]

yeah, make mrproper will create the $KBUILD_OUTPUT dir

[rlmenge]

Commits were super easy to follow, thank you! The logic makes sense to me but would want to validate in an rpmbuild environment to be sure all the KBUILD_OUTPUTs are operating as expected.

From what I gather with the spec is that it builds both secure and normal lvbs using the patches listed in the "kernel-lvbs.patches" and setting KBUILD_OUTPUT respectively. It then also builds Microsoft/skloader and Microsoft/initrd-sk.cpio.

A lot of the clean up work looks good to me such as making the config check its own function and reordering the manipulation of the config. Would just want again ensure the function is called as expected.

Just need to also update License files and Manifests similar to kernel-rt and that will clear up the failing github checks

[ddstreet]

Great to see the start of this, @ddstreet! I know we're mutually interested in seeing an LVBS-enabled kernel make its way into the extended repo.

Let us know when you're ready to start getting any early reviews/feedback on the PR. (I see it currently marked as WIP and draft.) I'm assuming @rlmenge, among others, will be keenly interested and have good suggestions.

Thanks! It should be ready for initial review; I'll fix the failing checks and then remove the wip/draft. However, it's not yet ready for merging as it does still need to change over to use the dedicated tarball instead of separate patches.

[ddstreet]

Commits were super easy to follow, thank you! The logic makes sense to me but would want to validate in an rpmbuild environment to be sure all the KBUILD_OUTPUTs are operating as expected.

From what I gather with the spec is that it builds both secure and normal lvbs using the patches listed in the "kernel-lvbs.patches" and setting KBUILD_OUTPUT respectively. It then also builds Microsoft/skloader and Microsoft/initrd-sk.cpio.

yep, correct

A lot of the clean up work looks good to me such as making the config check its own function and reordering the manipulation of the config. Would just want again ensure the function is called as expected.

Just need to also update License files and Manifests similar to kernel-rt and that will clear up the failing github checks

thanks, will do this now