Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. You opened a range of bugs in the same pass, other than most others - this one seems to refer to older qemu/kernel versions. Here you really need to specify what you'd need where - otherwise all we can do is consider that already fixed. TL;DR: linux 5.13 is in Ubuntu 21.10 [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Tags added: intel-bug-december-2021 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954469 Title: KVM Bus Lock Debug Exception Status in linux package in Ubuntu: Fix Released Bug description: A bus lock is acquired either through split locked access to writeback (WB) memory or by using locks to uncacheable (UC) memory. This is typically > 1000 cycles slower than atomic operation within a cache line. It also disrupts performance on other cores (which must wait for the bus lock to be released before their memory operations). Bus lock debug exception is a sub-feature of bus lock detection. It is an ability to notify the kernel by an #DB trap after the instruction acquires a bus lock when CPL>0. This allows the kernel to enforce user application throttling or mitigations. A logical processor can be configured to generate a debug exception (#DB) following acquisition of a bus lock. Software enables those debug exceptions by setting bit 2 of the IA32_DEBUGCTL MSR. The CPU enumerates this feature using CPUID.(EAX=7, ECX=0).ECX[24]. A debug exception due to acquistion of a bus lock is reported as a trap following execution of the instruction acquiring the bus lock. The processor identifies such debug exceptions using bit 11 of DR6: delivery of a bus-lock #DB clears DR6[11]. Linux 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
