From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: digitaleric@google.com
Subject: Re: [PATCH 0/3] Infinite loops in microcode while running guests
Date: Wed, 11 Nov 2015 07:47:50 -0500 [thread overview]
Message-ID: <564338F6.3070207@gmail.com> (raw)
In-Reply-To: <1447158174-10484-1-git-send-email-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
On 2015-11-10 07:22, Paolo Bonzini wrote:
> Yes, these can happen. The issue is that benign exceptions are
> delivered serially, but two of them (#DB and #AC) can also happen
> during exception delivery itself. The subsequent infinite stream
> of exceptions causes the processor to never exit guest mode.
>
> Paolo
>
> Eric Northup (1):
> KVM: x86: work around infinite loop in microcode when #AC is delivered
>
> Paolo Bonzini (2):
> KVM: svm: unconditionally intercept #DB
> KVM: x86: rename update_db_bp_intercept to update_bp_intercept
>
> arch/x86/include/asm/kvm_host.h | 2 +-
> arch/x86/include/uapi/asm/svm.h | 1 +
> arch/x86/kvm/svm.c | 22 +++++++++++-----------
> arch/x86/kvm/vmx.c | 7 +++++--
> arch/x86/kvm/x86.c | 2 +-
> 5 files changed, 19 insertions(+), 15 deletions(-)
>
I just finished running a couple of tests in a KVM instance running
nested on a Xen HVM instance, and found no issues, so for the set as a
whole:
Tested-by: Austin S. Hemmelgarn <ahferroin7@gmail.com>
Now to hope the equivalent fix for Xen gets into the Gentoo repositories
soon, as the issue propagates down through nested virtualization and
ties up the CPU regardless (and in turn triggers the watchdog).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-11-11 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 12:22 [PATCH 0/3] Infinite loops in microcode while running guests Paolo Bonzini
2015-11-10 12:22 ` [PATCH 1/3] KVM: x86: work around infinite loop in microcode when #AC is delivered Paolo Bonzini
2015-11-11 0:39 ` Venkatesh Srinivas
2015-11-10 12:22 ` [PATCH 2/3] KVM: svm: unconditionally intercept #DB Paolo Bonzini
2015-11-10 12:22 ` [PATCH 3/3] KVM: x86: rename update_db_bp_intercept to update_bp_intercept Paolo Bonzini
2015-11-10 15:38 ` [PATCH 0/3] Infinite loops in microcode while running guests Jan Kiszka
2015-11-10 16:09 ` Paolo Bonzini
2015-11-11 12:47 ` Austin S Hemmelgarn [this message]
2015-11-11 13:07 ` Paolo Bonzini
2015-11-11 13:12 ` Austin S Hemmelgarn
2015-11-12 14:08 ` Jan Kiszka
2015-11-12 14:37 ` Paolo Bonzini
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=564338F6.3070207@gmail.com \
--to=ahferroin7@gmail.com \
--cc=digitaleric@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).