From: Breno Leitao <leitao@debian.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Like Xu <like.xu@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Luwei Kang <luwei.kang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
rbc@meta.com
Subject: Re: [BUG] Guest OSes die simultaneously (bisected)
Date: Thu, 4 Jan 2024 02:01:00 -0800 [thread overview]
Message-ID: <ZZaB3CMiqkUU6qpG@gmail.com> (raw)
In-Reply-To: <3d8f5987-e09c-4dd2-a9c0-8ba22c9e948a@paulmck-laptop>
On Wed, Jan 03, 2024 at 02:22:23PM -0800, Paul E. McKenney wrote:
> I was
> therefore forced to bisect among the commits backported to the internal
> v5.19-based kernel, which fingered the backported version of the patch
> called out above.
Just to add some context to these backport, this commit (c59a1f106f5c)
was backported to the internal v5.19-based kernel in order to easily
backport these two fixes.
a16eb25b09c02a54c ("KVM: x86: Mask LVTPC when handling a PMI")
73554b29bd70546c1 ("KVM: x86/pmu: Synthesize at most one PMI per VM-exit")
They are required to solve the softlockup problem reported here:
https://lore.kernel.org/all/ZRwcpki67uhpAUKi@gmail.com/
prev parent reply other threads:[~2024-01-04 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 22:22 [BUG] Guest OSes die simultaneously (bisected) Paul E. McKenney
2024-01-03 23:27 ` Paul E. McKenney
2024-01-04 0:24 ` Sean Christopherson
2024-01-04 1:00 ` Paul E. McKenney
2024-01-04 14:50 ` Paul E. McKenney
2024-01-04 14:59 ` Paolo Bonzini
2024-01-04 16:06 ` Paul E. McKenney
2024-01-04 16:32 ` Paolo Bonzini
2024-01-04 17:25 ` Sean Christopherson
2024-01-04 19:23 ` Paul E. McKenney
2024-01-04 17:07 ` Andi Kleen
2024-01-04 10:01 ` Breno Leitao [this message]
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=ZZaB3CMiqkUU6qpG@gmail.com \
--to=leitao@debian.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=luwei.kang@intel.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rbc@meta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.