Skip to content

Conversation

@bchalios
Copy link
Contributor

Changes

This adds support for VMClock in our CI kernels. We use backported patches from here: https://lore.kernel.org/netdev/20251203123539.7292-1-bchalios@amazon.es/. Once these patches are picked up in mainline we'll drop the backported patches.

Reason

Allow merging #5564

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkbuild --all to verify that the PR passes
    build checks on all supported architectures.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

Add support to apply patches while build kernels for our CI. For the
time being we use this to apply patches for snapshot safety VMClock
extensions [1] (backported to 5.10 and 6.1 AL kernels).

[1] https://lkml.org/lkml/2025/12/3/653

Signed-off-by: Babis Chalios <bchalios@amazon.es>
Enable CONFIG_PTP_1588_CLOCK_VMCLOCK for both 5.10 and 6.1 kernels.

Signed-off-by: Babis Chalios <bchalios@amazon.es>
@bchalios bchalios added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Dec 18, 2025
@codecov
Copy link

codecov bot commented Dec 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.23%. Comparing base (f0691f8) to head (8bdaf9e).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5593   +/-   ##
=======================================
  Coverage   83.23%   83.23%           
=======================================
  Files         277      277           
  Lines       29263    29263           
=======================================
  Hits        24358    24358           
  Misses       4905     4905           
Flag Coverage Δ
5.10-m5n.metal 83.57% <ø> (ø)
5.10-m6a.metal 82.91% <ø> (+<0.01%) ⬆️
5.10-m6g.metal 80.19% <ø> (ø)
5.10-m6i.metal 83.57% <ø> (ø)
5.10-m7a.metal-48xl 82.90% <ø> (ø)
5.10-m7g.metal 80.19% <ø> (ø)
5.10-m7i.metal-24xl 83.54% <ø> (ø)
5.10-m7i.metal-48xl 83.54% <ø> (ø)
5.10-m8g.metal-24xl 80.18% <ø> (ø)
5.10-m8g.metal-48xl 80.18% <ø> (ø)
6.1-m5n.metal 83.60% <ø> (ø)
6.1-m6a.metal 82.95% <ø> (+<0.01%) ⬆️
6.1-m6g.metal 80.18% <ø> (-0.01%) ⬇️
6.1-m6i.metal 83.60% <ø> (ø)
6.1-m7a.metal-48xl 82.93% <ø> (ø)
6.1-m7g.metal 80.19% <ø> (ø)
6.1-m7i.metal-24xl 83.61% <ø> (ø)
6.1-m7i.metal-48xl 83.61% <ø> (-0.01%) ⬇️
6.1-m8g.metal-24xl 80.18% <ø> (ø)
6.1-m8g.metal-48xl 80.18% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bchalios bchalios enabled auto-merge (rebase) December 19, 2025 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Status: Awaiting review Indicates that a pull request is ready to be reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant