[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

2019-05-19 Thread quanxian
** Description changed: When bit 29 is set in Test Control MSR register 0x33, a #AC execption  is generated for split locked accesses at all CPL irrespective of  CR0.AM or EFLAGS.AC. This feature can help developers to capture memory accesses that across cachelines with #LOCK

[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

2019-05-09 Thread Robie Basak
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Changed in: qemu (Ubuntu) Importance: Undecided => Wishlist -- 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/1782209

[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

2019-05-07 Thread Paul Lai
Related QEMU patch can be found at: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg00507.html and related kvm-unit-test can be found at: https://patchwork.kernel.org/patch/10837677/ -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

2019-05-06 Thread Christian Ehrhardt 
Hi, I have not seen the kernel changes in 5.2 RCs - is there an update on their progress? Also any updates, links, commits on the related qemu contribution? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

2019-05-06 Thread quanxian
** Description changed: When bit 29 is set in Test Control MSR register 0x33, a #AC execption  is generated for split locked accesses at all CPL irrespective of  CR0.AM or EFLAGS.AC. This feature can help developers to capture memory accesses that across cachelines with #LOCK

[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable

2019-03-12 Thread Christian Ehrhardt 
My questions in comment #1 where no answered directly yet, but this still is using only kernel patches so far, I think it is time to add at least a kernel task. Furthermore it isn't upstream yet and the target being 5.2 is a bit out still, so I'd think you should target 19.10 ** Also affects: