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

fix todo: log virtio address #3592

Closed
wants to merge 7 commits into from

Conversation

sladyn98
Copy link
Contributor

@sladyn98 sladyn98 commented Apr 5, 2023

Changes

Resolves TODO: log address see #3273.

Reason

Resolves TODO.

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

  • If a specific issue led to this PR, this PR closes the issue.
  • The description of changes is clear and encompassing.
  • Any required documentation changes (code and docs) are included in this PR.
  • API changes follow the Runbook for Firecracker API changes.
  • User-facing changes are mentioned in CHANGELOG.md.
  • All added/changed functionality is tested.
  • New TODOs link to an issue.
  • Commits meet contribution quality standards.

  • This functionality cannot be added in rust-vmm.

@sladyn98
Copy link
Contributor Author

sladyn98 commented Apr 5, 2023

@roypat @JonathanWoollett-Light I fixed this in a new PR because the old PR kind of got messy with the signing of commits

@JonathanWoollett-Light JonathanWoollett-Light added Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled ` Type: Fix Indicates a fix to existing code labels Apr 13, 2023
@JonathanWoollett-Light
Copy link
Contributor

JonathanWoollett-Light commented Apr 13, 2023

I think the commit titled should be reworded, I would suggest: fix: log virtio address

@sladyn98 sladyn98 changed the title Fix TODO: Log virtio address fix todo: log virtio address Apr 14, 2023
@JonathanWoollett-Light
Copy link
Contributor

@sladyn98 Could you please rebase and resolve merge conflicts.

@sladyn98
Copy link
Contributor Author

@JonathanWoollett-Light Yeah sorry completely forgot about this : )

@sladyn98 sladyn98 force-pushed the fix-todo branch 2 times, most recently from 54d9917 to 63088fa Compare June 19, 2023 22:18
Signed-off-by: sladynnunes <snunes@usc.edu>
@sladyn98
Copy link
Contributor Author

@JonathanWoollett-Light Changed commit name and resolved conflicts

@codecov
Copy link

codecov bot commented Aug 21, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.01% ⚠️

Comparison is base (6bf22c2) 82.66% compared to head (b54724a) 82.66%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3592      +/-   ##
==========================================
- Coverage   82.66%   82.66%   -0.01%     
==========================================
  Files         221      221              
  Lines       28192    28191       -1     
==========================================
- Hits        23306    23305       -1     
  Misses       4886     4886              
Flag Coverage Δ
4.14-c7g.metal 78.12% <0.00%> (+<0.01%) ⬆️
4.14-m5d.metal 79.91% <0.00%> (+<0.01%) ⬆️
4.14-m6a.metal 79.05% <0.00%> (+<0.01%) ⬆️
4.14-m6g.metal 78.12% <0.00%> (+<0.01%) ⬆️
4.14-m6i.metal 79.90% <0.00%> (+<0.01%) ⬆️
5.10-c7g.metal 81.07% <0.00%> (+<0.01%) ⬆️
5.10-m5d.metal 82.59% <0.00%> (-0.01%) ⬇️
5.10-m6a.metal 81.84% <0.00%> (+<0.01%) ⬆️
5.10-m6g.metal 81.07% <0.00%> (+<0.01%) ⬆️
5.10-m6i.metal 82.59% <0.00%> (+<0.01%) ⬆️
6.1-c7g.metal 81.07% <0.00%> (+<0.01%) ⬆️
6.1-m5d.metal 82.59% <0.00%> (-0.01%) ⬇️
6.1-m6a.metal 81.84% <0.00%> (+<0.01%) ⬆️
6.1-m6g.metal 81.07% <0.00%> (+<0.01%) ⬆️
6.1-m6i.metal 82.59% <0.00%> (+<0.01%) ⬆️

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

Files Changed Coverage Δ
src/vmm/src/devices/virtio/queue.rs 94.65% <0.00%> (+0.29%) ⬆️

... and 1 file with indirect coverage changes

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

@xmarcalx
Copy link
Contributor

Hi @sladyn98 ,

This PR has still some style issue and not passing the PR. Are yous till interested in fix those issues and merge your changes?

roypat pushed a commit to roypat/firecracker that referenced this pull request May 8, 2024
Resolve a TODO for logging the address of a descriptor chain head if
fetching it from guest memory fails.

Closes firecracker-microvm#3592

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Co-Authored-By: sladynnunes <snunes@usc.edu>
roypat pushed a commit to roypat/firecracker that referenced this pull request May 8, 2024
Resolve a TODO for logging the address of a descriptor chain head if
fetching it from guest memory fails.

Closes firecracker-microvm#3592

Co-Authored-By: sladynnunes <snunes@usc.edu>
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
@roypat roypat closed this in 5a6424d May 14, 2024
brandonpike pushed a commit to brandonpike/firecracker that referenced this pull request May 20, 2024
Resolve a TODO for logging the address of a descriptor chain head if
fetching it from guest memory fails.

Closes firecracker-microvm#3592

Co-Authored-By: sladynnunes <snunes@usc.edu>
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
brandonpike pushed a commit to brandonpike/firecracker that referenced this pull request May 20, 2024
Resolve a TODO for logging the address of a descriptor chain head if
fetching it from guest memory fails.

Closes firecracker-microvm#3592

Co-Authored-By: sladynnunes <snunes@usc.edu>
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
brandonpike pushed a commit to brandonpike/firecracker that referenced this pull request May 20, 2024
Resolve a TODO for logging the address of a descriptor chain head if
fetching it from guest memory fails.

Closes firecracker-microvm#3592

Co-Authored-By: sladynnunes <snunes@usc.edu>
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled ` Type: Fix Indicates a fix to existing code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants