Skip to content

[bar-reloc 5/12] pci: Pass the BAR address to set_notification_ioevents() - #6090

Merged
ilstam merged 1 commit into
mainfrom
ilstam/bar-reloc-04-pass-bar-address
Aug 18, 2026
Merged

[bar-reloc 5/12] pci: Pass the BAR address to set_notification_ioevents()#6090
ilstam merged 1 commit into
mainfrom
ilstam/bar-reloc-04-pass-bar-address

Conversation

@ilstam

@ilstam ilstam commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Make set_notification_ioevents take the BAR base address as an argument
instead of reading it from config_bar_addr() itself. This will be needed
in subsequent commits where the BAR address stored in the config space
doesn't necessarily match the address used when ioeventfds were
registered (during BAR relocation).

No functional change intended.

Signed-off-by: Ilias Stamatis ilstam@amazon.com

@ilstam ilstam changed the title pci: Pass the BAR address to set_notification_ioevents() [bar-reloc 4/10] pci: Pass the BAR address to set_notification_ioevents() Aug 7, 2026
@ilstam
ilstam marked this pull request as ready for review August 7, 2026 15:19
@codecov

codecov Bot commented Aug 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.93%. Comparing base (ae1b9ee) to head (be7211d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6090   +/-   ##
=======================================
  Coverage   82.93%   82.93%           
=======================================
  Files         276      276           
  Lines       30846    30850    +4     
=======================================
+ Hits        25582    25586    +4     
  Misses       5264     5264           
Flag Coverage Δ
5.10-m5n.metal 83.19% <100.00%> (-0.01%) ⬇️
5.10-m6a.metal 82.55% <100.00%> (+<0.01%) ⬆️
5.10-m6g.metal 80.02% <100.00%> (+<0.01%) ⬆️
5.10-m6i.metal 83.19% <100.00%> (-0.01%) ⬇️
5.10-m7a.metal-48xl 82.55% <100.00%> (+<0.01%) ⬆️
5.10-m7g.metal 80.02% <100.00%> (+<0.01%) ⬆️
5.10-m7i.metal-24xl 83.17% <100.00%> (+<0.01%) ⬆️
5.10-m7i.metal-48xl 83.16% <100.00%> (-0.02%) ⬇️
5.10-m8g.metal-24xl 80.01% <100.00%> (+<0.01%) ⬆️
5.10-m8g.metal-48xl 80.01% <100.00%> (-0.01%) ⬇️
5.10-m8i.metal-48xl 83.17% <100.00%> (-0.01%) ⬇️
5.10-m8i.metal-96xl 83.17% <100.00%> (+<0.01%) ⬆️
6.1-m5n.metal 83.22% <100.00%> (-0.01%) ⬇️
6.1-m6a.metal 82.58% <100.00%> (-0.01%) ⬇️
6.1-m6g.metal 80.02% <100.00%> (+<0.01%) ⬆️
6.1-m6i.metal 83.22% <100.00%> (+<0.01%) ⬆️
6.1-m7a.metal-48xl 82.57% <100.00%> (+<0.01%) ⬆️
6.1-m7g.metal 80.01% <100.00%> (-0.01%) ⬇️
6.1-m7i.metal-24xl 83.23% <100.00%> (-0.01%) ⬇️
6.1-m7i.metal-48xl 83.23% <100.00%> (+<0.01%) ⬆️
6.1-m8g.metal-24xl 80.01% <100.00%> (+<0.01%) ⬆️
6.1-m8g.metal-48xl 80.01% <100.00%> (+<0.01%) ⬆️
6.1-m8i.metal-48xl 83.24% <100.00%> (+<0.01%) ⬆️
6.1-m8i.metal-96xl 83.23% <100.00%> (-0.01%) ⬇️
6.18-m5n.metal 83.22% <100.00%> (+<0.01%) ⬆️
6.18-m6a.metal 82.58% <100.00%> (-0.01%) ⬇️
6.18-m6g.metal 80.02% <100.00%> (+<0.01%) ⬆️
6.18-m6i.metal 83.22% <100.00%> (+<0.01%) ⬆️
6.18-m7a.metal-48xl 82.57% <100.00%> (+<0.01%) ⬆️
6.18-m7g.metal 80.02% <100.00%> (+<0.01%) ⬆️
6.18-m7i.metal-24xl 83.23% <100.00%> (-0.01%) ⬇️
6.18-m7i.metal-48xl 83.23% <100.00%> (-0.01%) ⬇️
6.18-m8g.metal-24xl 80.01% <100.00%> (+<0.01%) ⬆️
6.18-m8g.metal-48xl 80.01% <100.00%> (-0.01%) ⬇️
6.18-m8i.metal-48xl 83.23% <100.00%> (-0.01%) ⬇️
6.18-m8i.metal-96xl 83.24% <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 Harness.
📢 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.

@ilstam
ilstam force-pushed the ilstam/bar-reloc-04-pass-bar-address branch from 360ff13 to a677992 Compare August 10, 2026 17:58
ShadowCurse
ShadowCurse previously approved these changes Aug 11, 2026
Manciukic
Manciukic previously approved these changes Aug 12, 2026
@Manciukic

Copy link
Copy Markdown
Contributor

It looks like CI is failing at this PR in the stack: ERROR integration_tests/functional/test_max_devices.py::test_attach_maximum_devices[vmlinux-5.10.260-PCI_ON] - TimeoutError: Process 1286 did not exit within 10.0s

@ilstam

ilstam commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

It looks like CI is failing at this PR in the stack: ERROR integration_tests/functional/test_max_devices.py::test_attach_maximum_devices[vmlinux-5.10.260-PCI_ON] - TimeoutError: Process 1286 did not exit within 10.0s

Flaky failure? It passed after re-running.

@ilstam
ilstam force-pushed the ilstam/bar-reloc-04-pass-bar-address branch from a677992 to fcbc0f8 Compare August 14, 2026 16:49
@ilstam
ilstam force-pushed the ilstam/bar-reloc-04-pass-bar-address branch from fcbc0f8 to 0683e42 Compare August 14, 2026 16:49
@ilstam
ilstam dismissed stale reviews from Manciukic and ShadowCurse via 0683e42 August 14, 2026 16:50
@ilstam ilstam changed the title [bar-reloc 4/10] pci: Pass the BAR address to set_notification_ioevents() [bar-reloc 5/12] pci: Pass the BAR address to set_notification_ioevents() Aug 14, 2026
@ilstam
ilstam force-pushed the ilstam/bar-reloc-04-pass-bar-address branch from 0683e42 to 1889637 Compare August 17, 2026 10:23
@Manciukic

Copy link
Copy Markdown
Contributor

Flaky failure? It passed after re-running.

Can we please track these failures internally? We can't have flaky failures accumulate with nobody fixing them. The CI failed on a different flake now...

@ilstam

ilstam commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

Flaky failure? It passed after re-running.

Can we please track these failures internally? We can't have flaky failures accumulate with nobody fixing them. The CI failed on a different flake now...

I have created internal tracking tickets for all of them.

@ilstam
ilstam added this pull request to the merge queue Aug 18, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue because the pull requests in the stack were not ordered correctly in the queue Aug 18, 2026
@ilstam
ilstam added this pull request to the merge queue Aug 18, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue because the pull requests in the stack were not ordered correctly in the queue Aug 18, 2026
@ilstam
ilstam force-pushed the ilstam/bar-reloc-04-pass-bar-address branch from 1889637 to 6ffebd1 Compare August 18, 2026 17:21
@ilstam
ilstam added this pull request to the merge queue Aug 18, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue because the pull requests in the stack were not ordered correctly in the queue Aug 18, 2026
@ilstam
ilstam force-pushed the ilstam/bar-reloc-04-pass-bar-address branch from 6ffebd1 to e227ab8 Compare August 18, 2026 19:30
Base automatically changed from ilstam/bar-reloc-03-bus-move-range to main August 18, 2026 21:04
Make set_notification_ioevents take the BAR base address as an argument
instead of reading it from config_bar_addr() itself. This will be needed
in subsequent commits where the BAR address stored in the config space
doesn't necessarily match the address used when ioeventfds were
registered (during BAR relocation).

No functional change intended.

PR: #6090

Signed-off-by: Ilias Stamatis <ilstam@amazon.com>
@ilstam
ilstam force-pushed the ilstam/bar-reloc-04-pass-bar-address branch from e227ab8 to be7211d Compare August 18, 2026 21:04
@ilstam
ilstam added this pull request to the merge queue Aug 18, 2026
Merged via the queue into main with commit 0a745de Aug 18, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants