From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2] KVM: Synthesize G bit for all segments.
Date: Fri, 11 Jul 2014 09:09:57 +0200
Message-ID: <53BF8DC5.8090201@redhat.com>
References: <1405062495.12694.7.camel@akataria-dtop.eng.vmware.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jan Kiszka <jan.kiszka@siemens.com>, kvm@vger.kernel.org,
	Joerg Roedel <joro@8bytes.org>, Gleb Natapov <gleb@kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	jmattson@vmware.com
To: Alok Kataria <akataria@vmware.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:9088 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751762AbaGKHNe (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 11 Jul 2014 03:13:34 -0400
In-Reply-To: <1405062495.12694.7.camel@akataria-dtop.eng.vmware.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Il 11/07/2014 09:08, Alok Kataria ha scritto:
> +       /*
> +        * AMD CPUs circa 2014 track the G bit for all segments except CS.
> +        * However, the SVM spec states that the G bit is not observed by the
> +        * CPU, and some VMware virtual CPUs drop the G bit for all segments.
> +        * So let's synthesize a legal G bit for all segments, this helps
> +        * running KVM nested. It also helps cross-vendor migration, because
> +        * Intel's vmentry has a check on the 'G' bit.
> +        */

Good, I updated the patch.  I am picking it up.

Paolo