From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>, Liran Alon <liran.alon@oracle.com>
Cc: kvm list <kvm@vger.kernel.org>, Oliver Upton <oupton@google.com>
Subject: Re: [PATCH v2] kvm: x86: Add logical CPU to KVM_EXIT_FAIL_ENTRY info
Date: Mon, 16 Dec 2019 18:51:47 +0100 [thread overview]
Message-ID: <a319d0be-db7e-9650-62da-d70b2cc53709@redhat.com> (raw)
In-Reply-To: <CALMp9eTQf-htu-6R=VM+r8VmeBPwrVZArJaU6MnGD2m3hn+6jQ@mail.gmail.com>
On 16/12/19 18:43, Jim Mattson wrote:
> That's a good point. We had one case of numerous VM-exits for INIT,
> and I'm pretty sure that was a defective CPU too.
We too, and that's the only conclusion we could reach. And the other
one that I can remember was KVM_INTERNAL_ERROR_DELIVERY_EV with
EPT_VIOLATION exits, so I would add it to all KVM_EXIT_INTERNAL_ERROR.
Nowadays KVM_EXIT_FAIL_ENTRY would probably also be an internal error,
however it was somewhat more frequent back before Intel CPUs had
unrestricted guest support.
Paolo
prev parent reply other threads:[~2019-12-16 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 0:20 [PATCH v2] kvm: x86: Add logical CPU to KVM_EXIT_FAIL_ENTRY info Jim Mattson
2019-12-14 1:10 ` Liran Alon
2019-12-16 17:43 ` Jim Mattson
2019-12-16 17:51 ` Paolo Bonzini [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=a319d0be-db7e-9650-62da-d70b2cc53709@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=oupton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox