Address performance issue w/ GICv4-based guests
Bug #1829942 reported by
dann frazier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
dann frazier | ||
Cosmic |
Invalid
|
Undecided
|
dann frazier | ||
Disco |
Fix Released
|
Undecided
|
dann frazier | ||
Eoan |
Fix Released
|
Undecided
|
dann frazier |
Bug Description
[Impact]
Performance is degraded when a guest is booted w/ vgic v4 support enabled.
[Test Case]
I used a HiSilicon D06 system w/ an Intel 82599 10Gbps NIC. I passed through a VF to a guest, and ran "netperf -H <host>" against a 10Gbps-capable target. With vgic v4 support, I'm only seeing 5-6Gbps. With vgic v3 support, this was in the 9Gbps spectrum. And, after applying the upstream fix, I'm also seeing >9Gbps w/ vgic v4 enabled.
Note: to enable vgic v4 support, pass "kvm-arm.
[Fix]
ca71228b42a96 arm64: KVM: Always set ICH_HCR_EL2.EN if GICv4 is enabled
[Regression Risk]
The fix is restricted to the ARM/KVM subsystem.
Changed in linux (Ubuntu Eoan): | |
status: | Incomplete → In Progress |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu Disco): | |
status: | New → In Progress |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu Cosmic): | |
status: | New → In Progress |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu Cosmic): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-cosmic verification-done-di removed: verification-needed-cosmic |
tags: |
added: verification-done-disco removed: verification-done-di |
Changed in linux (Ubuntu Cosmic): | |
status: | Fix Committed → Invalid |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1829942
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.