On Tue, Sep 17, 2019 at 03:36:00PM +0200, Paolo Bonzini wrote: > On 12/09/19 09:59, James Harvey wrote: > > Yes, confirmed reverting this commit (to restore the originally > > reverted commit) fixes the issue. > > > > I'm really surprised to have not found similar reports, especially of > > Arch users which had 5.2.11 put into the repos on Aug 29. Makes me > > wonder if it's reproducible on all hardware using host hyperthreading > > and giving a VM > nproc/2 virtual cpus. > > > > In the meantime, what should go into distro decisions on whether to > > revert? Since you mentioned: "Reverting the revert isn't a viable > > solution." > > Hi James, > > the fix (which turned out to be livelock) is now part of 5.3. You > should expect it sometime soon in 5.2 stable kernels. > > commit 002c5f73c508f7df5681bda339831c27f3c1aef4 > KVM: x86/mmu: Reintroduce fast invalidate/zap for flushing memslot Will be in the next 5.2-stable release in a few days. thanks, greg k-h
