Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 138
    • Issues 138
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Issues
  • #533

Closed
Open
Created Apr 06, 2022 by Ricardo Cañuelo Navarro@hardboprobotContributor

RFC: allow specifying CPU microcode binaries in jobs

The Linux kernel provides a mechanism to load CPU microcodes in the early boot stages. This may be useful for some target platforms that need certain ucode updates to enable vulnerability mitigation mechanisms or other specific CPU features.

The most flexible method to load them (at boot time) is to prepend the cpio'd ucode binary to the initrd image. Having an optional "deploy" key for this that makes LAVA concatenate the ucode binary with the repackaged initrd (after the overlays have been applied) would allow to boot Linux with additional CPU ucodes in certain platforms, configurable in a per-job basis without having to change anything in the kernel image or the initrd.

I tried to do this myself but I couldn't find how to modify the job definition schema so that the validation won't warn about the extra key. All guidance is welcome.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking