Performing verification for Jammy

I deployed a bare metal host, and installed a KVM stack just like the testcase
section.

Sapphire Rapids Intel(R) Xeon(R) Platinum 8468
22.04 LTS Jammy

5.15.0-130-generic

Outside VM
cpuid 2784
cpuid 2699
cpuid 2699
cpuid 2797
cpuid 2866

Inside VM
cpuid 52891
cpuid 51100
cpuid 50767
cpuid 55294
cpuid 52449

I then enabled -proposed on both the bare metal system and the VM, and installed
5.15.0-132-generic.

$ uname -rv
5.15.0-132-generic #143-Ubuntu SMP Wed Jan 15 20:39:05 UTC 2025

I then re-ran the tests:

5.15.0-132-generic

Outside VM
cpuid 2698
cpuid 2700
cpuid 2698
cpuid 2797
cpuid 2869

Inside VM
cpuid 20481
cpuid 20541
cpuid 20494
cpuid 20444
cpuid 20474

As we can see, Outside VM testcases are stable, while Inside VM performance
has improved by what we expected, going from around 52,000 to 20,000.

The kernel in -proposed solves the problem, happy to mark verified for
Jammy.

** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2093146

Title:
  KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter
  and VM-Exit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093146/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to