From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Habkost Subject: Re: [PATCH 0/2] i386: arch_capabilities fixes + migratability Date: Wed, 20 Mar 2019 12:18:53 -0300 Message-ID: <20190320151853.GO8899@habkost.net> References: <20190125220606.4864-1-ehabkost@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, Radim =?utf-8?B?S3LEjW3DocWZ?= , Marcelo Tosatti , Robert Hoo , Tao Xu , Paolo Bonzini , Richard Henderson To: qemu-devel@nongnu.org Return-path: Content-Disposition: inline In-Reply-To: <20190125220606.4864-1-ehabkost@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel2=m.gmane.org@nongnu.org Sender: "Qemu-devel" List-Id: kvm.vger.kernel.org It looks like this has slipped through the cracks. I'm queueing this series for -rc1. On Fri, Jan 25, 2019 at 08:06:04PM -0200, Eduardo Habkost wrote: > 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 > -- Eduardo