From: Sean Christopherson <seanjc@google.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Wu Zongyo <wuzongyo@mail.ustc.edu.cn>
Subject: Re: [PATCH 0/2] KVM: SVM: Fix unexpected #UD on INT3 in SEV guests
Date: Thu, 24 Aug 2023 09:08:15 -0700 [thread overview]
Message-ID: <ZOeAb0ccVjdw3Gvw@google.com> (raw)
In-Reply-To: <ZOZ2KqCIcleJxrTz@google.com>
On Wed, Aug 23, 2023, Sean Christopherson wrote:
> One idea to make the original bug repro on every run would be to constantly
> toggle nx_huge_pages between "off" and "force" while the guest is booting. Toggling
> nx_huge_pages should force KVM to rebuild the SPTEs and all but guarantee trying
> to deliver the #BP will hit a #NPF.
Mwhahaha. That, plus a delay in the guest and disabling THP, makes this 100%
reproducible. I'll verify the fix actually works before posting v2.
prev parent reply other threads:[~2023-08-24 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 23:49 [PATCH 0/2] KVM: SVM: Fix unexpected #UD on INT3 in SEV guests Sean Christopherson
2023-08-10 23:49 ` [PATCH 1/2] KVM: SVM: Don't inject #UD if KVM attempts emulation of SEV guest w/o insn Sean Christopherson
2023-08-10 23:49 ` [PATCH 2/2] KVM: SVM: Require nrips support for SEV guests (and beyond) Sean Christopherson
2023-08-22 13:55 ` [PATCH 0/2] KVM: SVM: Fix unexpected #UD on INT3 in SEV guests Tom Lendacky
2023-08-22 15:14 ` Sean Christopherson
2023-08-23 16:18 ` Tom Lendacky
2023-08-23 20:03 ` Sean Christopherson
2023-08-23 20:36 ` Tom Lendacky
2023-08-23 21:12 ` Sean Christopherson
2023-08-24 16:08 ` Sean Christopherson [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=ZOeAb0ccVjdw3Gvw@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thomas.lendacky@amd.com \
--cc=wuzongyo@mail.ustc.edu.cn \
/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.