You see in the referred upstream commits, this is how it landed And keeping the patches close to as it is upstream helps
Otherwise one wonders why it is different than in the original commit simplified explanation of the timeline 1. orginal code always exposed the capability 2. new code does mpt exposed it on AMD depending on CPUID_7_0_EDX_ARCH_CAPABILITIES 3. Even newer code made this controllable via a flag that is controlled by the machine type - so it can behave old or new way. => That code that was added and then removed actually only got moved to another place where it can be behind this controllable compat flag. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2131822 Title: Known Windows 11 KVM Issue AMD KMODE Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2131822/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
