From: Andi Kleen <ak@linux.intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Like Xu <like.xu@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Luwei Kang <luwei.kang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Breno Leitao <leitao@debian.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [BUG] Guest OSes die simultaneously (bisected)
Date: Thu, 4 Jan 2024 09:07:56 -0800 [thread overview]
Message-ID: <ZZbl7KqomDOR+HUC@tassilo> (raw)
In-Reply-To: <b2775ea5-20c9-4dff-b4b1-bbb212065a22@paulmck-laptop>
> My (completely random) guess is that there is some rare combination
> of events that causes this code to fail. If so, is it feasible to
> construct a test that makes this rare combination of events less rare,
> so that similar future bugs are caught more quickly?
Yes, I tested something similar before. What you need is create lots of
PMIs with perf (running perf top should be enough) and a workload that creates
lots of exits in a guest (e.g. running fio on a virtio device). This
will stress test this particular path.
-Andi
next prev parent reply other threads:[~2024-01-04 17:08 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 [this message]
2024-01-04 10:01 ` Breno Leitao
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=ZZbl7KqomDOR+HUC@tassilo \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=leitao@debian.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=seanjc@google.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.