From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/2] KVM: x86 emulator: emulate MOVAPS and MOVAPD SSE
 instructions
Date: Tue, 18 Mar 2014 13:11:47 +0100
Message-ID: <53283803.5010209@redhat.com>
References: <1394913720-6466-1-git-send-email-imammedo@redhat.com> <8569d2b4-0593-4f7a-859c-3848670f718d@email.android.com> <5326C0C3.6000105@redhat.com> <fb38ff9d-8c00-4b02-b0da-2db989f7190e@email.android.com> <53272A53.8090605@redhat.com> <53273309.8060103@zytor.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gleb@kernel.org, tglx@linutronix.de, mingo@redhat.com,
	x86@kernel.org, kvm@vger.kernel.org
To: "H. Peter Anvin" <hpa@zytor.com>,
	Igor Mammedov <imammedo@redhat.com>,
	linux-kernel@vger.kernel.org
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <53273309.8060103@zytor.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

Il 17/03/2014 18:38, H. Peter Anvin ha scritto:
> I'm not sure what you mean with "valid real mode selectors"; the normal
> case in big real mode is that either CS = SS = 0 or CS = SS = <some
> program base address>.

I mean "valid according to the VMX spec" for running in vm86 mode: base 
= selector << 4, limit = 0xffff, access rights = 0xf3.

If a segment does not follow the rules, but CS does, we could run the 
guest normally and trap memory accesses to KVM.

Paolo