public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: James Harvey <jamespharvey20@gmail.com>,
	Sean Christopherson <sean.j.christopherson@intel.com>
Cc: kvm@vger.kernel.org, Alex Willamson <alex.williamson@redhat.com>,
	gregkh@linuxfoundation.org
Subject: Re: 5.2.11+ Regression: > nproc/2 lockups during initramfs
Date: Tue, 17 Sep 2019 15:36:00 +0200	[thread overview]
Message-ID: <f897f18b-9a98-abeb-9caf-cfdca7e66124@redhat.com> (raw)
In-Reply-To: <CA+X5Wn4ngf92GEU=9fuxL1FVfPtq9tJE5D5VMBq6gGp5pd4Nkw@mail.gmail.com>

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

Thanks,

Paolo

  reply	other threads:[~2019-09-17 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08 10:37 5.2.11+ Regression: > nproc/2 lockups during initramfs James Harvey
2019-09-10 18:32 ` Sean Christopherson
2019-09-12  7:59   ` James Harvey
2019-09-17 13:36     ` Paolo Bonzini [this message]
2019-09-17 13:41       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f897f18b-9a98-abeb-9caf-cfdca7e66124@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jamespharvey20@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=sean.j.christopherson@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox