Conversation
EVE is removing its Xen hypervisor flavor (HV=xen, pkg/xen, the Xen toolstack and pillar's Xen backend). After that nothing in the rootfs talks to the Xen kernel interfaces: the only /dev/xen and /proc/xen probes were the hypervisor auto-detect and the Xen-specific init scripts, which go away with the flavor. Keeping CONFIG_XEN=y in a KVM-only OS is dead weight in the image and extra attack surface (dom0 backends, grant tables, pvcalls, xenbus). The defconfig is regenerated with savedefconfig so dependent options fall out consistently. Besides CONFIG_XEN_* the expanded .config loses only SYS_HYPERVISOR, HVC_IRQ and (on 5.10/5.15) PAGE_POOL, which xen-netfront alone was selecting. CONFIG_PARAVIRT (KVM steal-time accounting) was =y through XEN's select and stays =y; savedefconfig now has to list it explicitly. CONFIG_MMC_SDHCI_XENON is the Marvell SDHCI controller, not Xen, and stays. Intentional loss: EVE will no longer boot as a Xen guest. Signed-off-by: Paul Gaiduk <paulg@zededa.com> Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
Description
EVE is removing its Xen hypervisor flavor (
HV=xen,pkg/xen, the Xen toolstack and pillar's Xen backend). After that nothing in the EVE rootfs talks to the Xen kernel interfaces any more, soCONFIG_XEN=yis dead weight in the kernel image and extra attack surface (dom0 backends, grant tables, pvcalls, xenbus).This PR turns
CONFIG_XENoff inkernel/kernel-jammy-src/arch/arm64/configs/tegra_eveos_defconfigand regenerates the defconfig withsavedefconfig, so every option that depended on Xen falls out consistently instead of being hand-deleted.Options that were
=yonly becauseXENselected them keep their value and are now listed explicitly in the defconfig (the built kernel does not change for them):CONFIG_PARAVIRT.Draft until EVE's own Xen removal has landed; merging this earlier would break the
HV=xenEVE build on the next kernel bump.How to test and validate this PR
Expanded the old and the new defconfig to a full
.configinside thebuilderstage ofDockerfile.gccand diffed them: the only lines that differ areCONFIG_XEN*and the options Xen alone was selecting (listed in the commit message).grep XENon the new.configshows only# CONFIG_XEN is not set(plus unrelated symbols that merely contain the string, e.g.MMC_SDHCI_XENON).The regular
pr-buildworkflow on this PR is the build test.Changelog notes
EVE no longer boots as a Xen guest.
🤖 Generated with Claude Code