Skip to content
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

refactor(virtio-block): use a type for config space #5029

Merged

Conversation

ShadowCurse
Copy link
Contributor

Changes

Instead of using a vector of bytes as a config space it is better to use a proper type. This was already done in the virtio-net device, so just repeat same in block device.

Reason

Less manual bytes manipulations.

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 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.

@ShadowCurse ShadowCurse self-assigned this Feb 7, 2025
Copy link

codecov bot commented Feb 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.16%. Comparing base (44a50b4) to head (d6842af).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5029      +/-   ##
==========================================
- Coverage   83.16%   83.16%   -0.01%     
==========================================
  Files         245      245              
  Lines       26647    26642       -5     
==========================================
- Hits        22161    22156       -5     
  Misses       4486     4486              
Flag Coverage Δ
5.10-c5n.metal 83.61% <100.00%> (-0.01%) ⬇️
5.10-m5n.metal 83.59% <100.00%> (-0.01%) ⬇️
5.10-m6a.metal 82.80% <100.00%> (-0.01%) ⬇️
5.10-m6g.metal 79.59% <100.00%> (-0.01%) ⬇️
5.10-m6i.metal 83.58% <100.00%> (+<0.01%) ⬆️
5.10-m7g.metal 79.59% <100.00%> (-0.01%) ⬇️
6.1-c5n.metal 83.61% <100.00%> (+<0.01%) ⬆️
6.1-m5n.metal 83.58% <100.00%> (-0.01%) ⬇️
6.1-m6a.metal 82.80% <100.00%> (-0.01%) ⬇️
6.1-m6g.metal 79.59% <100.00%> (-0.01%) ⬇️
6.1-m6i.metal 83.58% <100.00%> (-0.01%) ⬇️
6.1-m7g.metal 79.59% <100.00%> (-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.

Instead of using a vector of bytes as a config space it is better to
use a proper type. This was already done in the virtio-net device,
so just repeat same in block device.

Signed-off-by: Egor Lazarchuk <[email protected]>
@ShadowCurse ShadowCurse force-pushed the virtio_block_config_space branch from 250c725 to c13cde4 Compare February 7, 2025 15:19
@ShadowCurse ShadowCurse marked this pull request as ready for review February 7, 2025 15:19
@ShadowCurse ShadowCurse added Status: Awaiting review Indicates that a pull request is ready to be reviewed Type: Enhancement Indicates new feature requests labels Feb 7, 2025
@zulinx86 zulinx86 merged commit b0e110b into firecracker-microvm:main Feb 7, 2025
6 of 7 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 Type: Enhancement Indicates new feature requests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants