From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, "Eduardo Habkost" <ehabkost@redhat.com>,
"Robert Hoo" <robert.hu@linux.intel.com>,
"Richard Henderson" <rth@twiddle.net>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Tao Xu" <tao5.xu@intel.com>
Subject: [Qemu-devel] [PATCH 0/2] i386: arch_capabilities fixes + migratability
Date: Fri, 25 Jan 2019 20:06:04 -0200 [thread overview]
Message-ID: <20190125220606.4864-1-ehabkost@redhat.com> (raw)
This series works around KVM bugs that affect the arch_capabilities
feature. One bug made the feature be enabled incorrect on AMD hosts,
and another one made the feature unsafe to enable on most Intel hosts.
With the work around, we can finally make arch_capabilities a migratable
feature.
Unfortunately, the work around has the side effect of making
arch_capabilities unavailable on hosts without hardware support for the
feature until one of the KVM bugs is fixed.
Eduardo Habkost (2):
i386: kvm: Disable arch_capabilities if MSR can't be set
i386: Make arch_capabilities migratable
target/i386/cpu.c | 1 -
target/i386/kvm.c | 9 +++++++++
2 files changed, 9 insertions(+), 1 deletion(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2019-01-25 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 22:06 Eduardo Habkost [this message]
2019-01-25 22:06 ` [Qemu-devel] [PATCH 1/2] i386: kvm: Disable arch_capabilities if MSR can't be set Eduardo Habkost
2019-01-25 22:06 ` [Qemu-devel] [PATCH 2/2] i386: Make arch_capabilities migratable Eduardo Habkost
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=20190125220606.4864-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=robert.hu@linux.intel.com \
--cc=rth@twiddle.net \
--cc=tao5.xu@intel.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).