Skip to content

Conversation

bchalios
Copy link
Contributor

@bchalios bchalios commented Aug 1, 2025

Changes

Remove unused code from pci crate. Also, simplify code in VirtIO PCI transport introducing stronger assumptions about the fact that we are always using a single 64bit BAR for VirtIO devices

Reason

Simplify code and remove dead code.

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.

@bchalios bchalios enabled auto-merge (rebase) August 1, 2025 12:00
We are vending PCI code taken from Cloud Hypervisor's implementation.
There is code in there that we don't actually use. So drop it to reduce
the dead code in the project.

Signed-off-by: Babis Chalios <[email protected]>
Cloud Hypervisor code is passing a resource type argument in the logic
that allocates BARs for devices. `Resource` is an Enum where one of its
variants is `PciBar`. Not sure what Cloud Hypervisor uses this for, but
it seems redundant since this method is specifically used to allocate
BAR memory for devices.

We definitely don't use it, so remove it.

Signed-off-by: Babis Chalios <[email protected]>
Despite the fact we are using a single 64bit MMIO BARs for VirtIO
devices, we had code that allowed for multiple BARs including BARs of
other types (IO and 32bit MMIO). Remove this code and always assume we
are only using 64bit BAR at index 0.

Signed-off-by: Babis Chalios <[email protected]>
@bchalios bchalios added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Aug 1, 2025
Copy link

codecov bot commented Aug 1, 2025

Codecov Report

❌ Patch coverage is 75.51020% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.68%. Comparing base (c2e4088) to head (d8b8d1f).
⚠️ Report is 3 commits behind head on feature/pcie.

Files with missing lines Patch % Lines
src/vmm/src/devices/virtio/transport/pci/device.rs 71.42% 12 Missing ⚠️
Additional details and impacted files
@@               Coverage Diff                @@
##           feature/pcie    #5342      +/-   ##
================================================
+ Coverage         80.36%   80.68%   +0.32%     
================================================
  Files               265      265              
  Lines             30828    30650     -178     
================================================
- Hits              24775    24731      -44     
+ Misses             6053     5919     -134     
Flag Coverage Δ
5.10-c5n.metal 80.47% <75.51%> (+0.35%) ⬆️
5.10-m5n.metal 80.47% <75.51%> (+0.35%) ⬆️
5.10-m6a.metal 79.69% <75.51%> (+0.36%) ⬆️
5.10-m6g.metal 76.99% <75.51%> (+0.34%) ⬆️
5.10-m6i.metal 80.47% <75.51%> (+0.35%) ⬆️
5.10-m7a.metal-48xl 79.67% <75.51%> (+0.35%) ⬆️
5.10-m7g.metal 76.99% <75.51%> (+0.34%) ⬆️
5.10-m7i.metal-24xl 80.44% <75.51%> (+0.35%) ⬆️
5.10-m7i.metal-48xl 80.44% <75.51%> (+0.35%) ⬆️
5.10-m8g.metal-24xl 76.98% <75.51%> (+0.34%) ⬆️
5.10-m8g.metal-48xl 76.98% <75.51%> (+0.34%) ⬆️
6.1-c5n.metal 80.51% <75.51%> (+0.35%) ⬆️
6.1-m5n.metal 80.51% <75.51%> (+0.35%) ⬆️
6.1-m6a.metal 79.73% <75.51%> (+0.36%) ⬆️
6.1-m6g.metal 76.99% <75.51%> (+0.34%) ⬆️
6.1-m6i.metal 80.51% <75.51%> (+0.35%) ⬆️
6.1-m7a.metal-48xl 79.72% <75.51%> (+0.36%) ⬆️
6.1-m7g.metal 76.99% <75.51%> (+0.34%) ⬆️
6.1-m7i.metal-24xl 80.52% <75.51%> (+0.35%) ⬆️
6.1-m7i.metal-48xl 80.52% <75.51%> (+0.35%) ⬆️
6.1-m8g.metal-24xl 76.99% <75.51%> (+0.34%) ⬆️
6.1-m8g.metal-48xl 76.98% <75.51%> (+0.34%) ⬆️

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 merged commit 97eaa9e into firecracker-microvm:feature/pcie Aug 4, 2025
7 of 8 checks passed
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.

3 participants