Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

refactor: use vmm_sys_util::timerfd module instead of timerfd crate #5424

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
roypat wants to merge 2 commits into firecracker-microvm:main
base: main
Choose a base branch
Loading
from roypat:rust-vmm-timerfd

Conversation

Copy link
Contributor

@roypat roypat commented Sep 2, 2025

Use vmm_sys_util's timerfd implementation instead of the one in the
timerfd crate. This eliminates a couple of dependencies, including an
aesthetically unpleasing double-dependency on different versions of
rustix.

This'll need to stay draft until rust-vmm/vmm-sys-util#254 is merged, a new vmm-sys-util release is made, and the entire rust-vmm ecosystem has updated to it (#5392), in which case the change to the top level Cargo.toml needs to be dropped.

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.

The variant was only constructed in a single place, so just make the
string that was passed there the display text for this error.
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Use vmm_sys_util's timerfd implementation instead of the one in the
timerfd crate. This eliminates a couple of dependencies, including an
aesthetically unpleasing double-dependency on different versions of
rustix.
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Copy link

codecov bot commented Sep 2, 2025
edited
Loading

Codecov Report

❌ Patch coverage is 91.30435% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.56%. Comparing base (4a21dc6) to head (1be7df7).
⚠️ Report is 3 commits behind head on main.

Files with missing lines Patch % Lines
src/vmm/src/devices/virtio/balloon/persist.rs 0.00% 2 Missing ⚠️
Additional details and impacted files
@@ Coverage Diff @@
## main #5424 +/- ##
==========================================
- Coverage 82.73% 82.56% -0.18% 
==========================================
 Files 263 263 
 Lines 27455 27444 -11 
==========================================
- Hits 22715 22658 -57 
- Misses 4740 4786 +46 
Flag Coverage Δ
5.10-m5n.metal 82.84% <91.30%> (+<0.01%) ⬆️
5.10-m6a.metal 82.08% <91.30%> (-0.01%) ⬇️
5.10-m6g.metal 79.32% <91.30%> (-0.21%) ⬇️
5.10-m6i.metal 82.83% <91.30%> (+<0.01%) ⬆️
5.10-m7a.metal-48xl 82.08% <91.30%> (-0.01%) ⬇️
5.10-m7g.metal 79.32% <91.30%> (-0.21%) ⬇️
5.10-m7i.metal-24xl 82.81% <91.30%> (-0.01%) ⬇️
5.10-m7i.metal-48xl 82.81% <91.30%> (+<0.01%) ⬆️
5.10-m8g.metal-24xl 79.31% <91.30%> (-0.21%) ⬇️
5.10-m8g.metal-48xl 79.31% <91.30%> (-0.21%) ⬇️
6.1-m5n.metal 82.88% <91.30%> (+<0.01%) ⬆️
6.1-m6a.metal 82.13% <91.30%> (+<0.01%) ⬆️
6.1-m6g.metal 79.31% <91.30%> (-0.22%) ⬇️
6.1-m6i.metal 82.87% <91.30%> (-0.01%) ⬇️
6.1-m7a.metal-48xl 82.12% <91.30%> (+<0.01%) ⬆️
6.1-m7g.metal 79.32% <91.30%> (-0.21%) ⬇️
6.1-m7i.metal-24xl 82.88% <91.30%> (-0.01%) ⬇️
6.1-m7i.metal-48xl 82.88% <91.30%> (-0.01%) ⬇️
6.1-m8g.metal-24xl 79.31% <91.30%> (-0.21%) ⬇️
6.1-m8g.metal-48xl 79.31% <91.30%> (-0.22%) ⬇️

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.

@roypat roypat changed the title (削除) refactor: use vmm_sys_util::timer module instead of timefd crate (削除ここまで) (追記) refactor: use vmm_sys_util::timerfd module instead of timerfd crate (追記ここまで) Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

1 participant

AltStyle によって変換されたページ (->オリジナル) /