From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] KVM: x86: don't expose syscall/sysret to intel 32-bit
 guest
Date: Wed, 25 Nov 2015 14:27:40 +0100
Message-ID: <5655B74C.6070305@redhat.com>
References: <BLU436-SMTP15906F5C0F0430EFB140F45801B0@phx.gbl>
 <564DACF5.9090908@redhat.com>
 <CANRm+CxoipUJEzx0MBMbG84GLmf_f+3fSs1YOPTwme2dwZ7UDA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: Wanpeng li <wanpeng.li@hotmail.com>, kvm <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
To: Wanpeng Li <kernellwp@gmail.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <CANRm+CxoipUJEzx0MBMbG84GLmf_f+3fSs1YOPTwme2dwZ7UDA@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org



On 25/11/2015 13:45, Wanpeng Li wrote:
> 2015-11-19 19:05 GMT+08:00 Paolo Bonzini <pbonzini@redhat.com>:
>>
>> 1) Clear F(SYSCALL) in kvm_update_cpuid, like you are doing here but
>> only if F(LM) is already clear (in addition to the vendor being Intel).
> 
> It seems that F(LM) is always set in the case of qemu-system-x86_64 w/
> 32-bit guest, vmware also exposes LM bit to 32 bit guest(however it
> doesn't expose syscall/sysret)

Does it expose the SYSCALL bit?

Paolo