Skip to content

Conversation

@kalyazin
Copy link
Contributor

@kalyazin kalyazin commented Dec 4, 2025

Changes

test(memory_overhead): update x86 mmio gap start

Reason

In the following commit we resized the 32b MMIO region to 1GiB, but it was not reflected in the test:

commit 7c623e89b4da8941ea8e8e37ca24676d90d3df67
Author: Babis Chalios <[email protected]>
Date:   Mon May 5 17:52:08 2025 +0200

    arch: define 64-bit capable MMIO memory regions

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.

@codecov
Copy link

codecov bot commented Dec 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.23%. Comparing base (86afedb) to head (c878c10).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5563      +/-   ##
==========================================
- Coverage   83.24%   83.23%   -0.01%     
==========================================
  Files         277      277              
  Lines       29263    29263              
==========================================
- Hits        24359    24358       -1     
- Misses       4904     4905       +1     
Flag Coverage Δ
5.10-m5n.metal 83.58% <ø> (+<0.01%) ⬆️
5.10-m6a.metal 82.91% <ø> (ø)
5.10-m6g.metal 80.19% <ø> (-0.01%) ⬇️
5.10-m6i.metal 83.57% <ø> (ø)
5.10-m7a.metal-48xl 82.91% <ø> (ø)
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.19% <ø> (ø)
5.10-m8g.metal-48xl 80.19% <ø> (-0.01%) ⬇️
6.1-m5n.metal 83.60% <ø> (-0.01%) ⬇️
6.1-m6a.metal 82.94% <ø> (-0.01%) ⬇️
6.1-m6g.metal 80.19% <ø> (ø)
6.1-m6i.metal 83.60% <ø> (-0.01%) ⬇️
6.1-m7a.metal-48xl 82.93% <ø> (ø)
6.1-m7g.metal 80.19% <ø> (+<0.01%) ⬆️
6.1-m7i.metal-24xl 83.61% <ø> (-0.01%) ⬇️
6.1-m7i.metal-48xl 83.62% <ø> (-0.01%) ⬇️
6.1-m8g.metal-24xl 80.18% <ø> (-0.01%) ⬇️
6.1-m8g.metal-48xl 80.19% <ø> (ø)

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.

@kalyazin kalyazin marked this pull request as ready for review December 4, 2025 20:29
@kalyazin kalyazin enabled auto-merge (rebase) December 4, 2025 20:29
@kalyazin kalyazin self-assigned this Dec 4, 2025
@kalyazin kalyazin added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Dec 4, 2025
In the following commit we resized the 32b MMIO region to 1GiB, but it
was not reflected in the test:

commit 7c623e8
Author: Babis Chalios <[email protected]>
Date:   Mon May 5 17:52:08 2025 +0200

    arch: define 64-bit capable MMIO memory regions

Signed-off-by: Nikita Kalyazin <[email protected]>
@kalyazin kalyazin changed the title test(memory_overhead): update x86 GAP start test(memory_overhead): update x86 mmio gap start Dec 5, 2025
@kalyazin kalyazin merged commit d130c7d into firecracker-microvm:main Dec 5, 2025
7 checks passed
@kalyazin kalyazin deleted the mem_overh branch December 5, 2025 16:09
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