From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] KVM: VMX: Require KVM_SET_TSS_ADDR being called prior to
 running a VCPU
Date: Mon, 18 Mar 2013 13:50:54 -0300
Message-ID: <20130318165054.GA12135@amt.cnet>
References: <5142D010.7060303@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Gleb Natapov <gleb@redhat.com>, kvm <kvm@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:10514 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751431Ab3CRQyn (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 18 Mar 2013 12:54:43 -0400
Content-Disposition: inline
In-Reply-To: <5142D010.7060303@web.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Fri, Mar 15, 2013 at 08:38:56AM +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Very old user space (namely qemu-kvm before kvm-49) didn't set the TSS
> base before running the VCPU. We always warned about this bug, but no
> reports about users actually seeing this are known. Time to finally
> remove the workaround that effectively prevented to call vmx_vcpu_reset
> while already holding the KVM srcu lock.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> This obsoletes all other attempts to allow vmx_vcpu_reset to be called
> with the srcu lock held. Hope we can settle the topic this way.

Applied, thanks.