All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
	Igor Mammedov <imammedo@redhat.com>,
	linux-kernel@vger.kernel.org
Cc: gleb@kernel.org, tglx@linutronix.de, mingo@redhat.com,
	x86@kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: x86 emulator: emulate MOVAPS and MOVAPD SSE instructions
Date: Tue, 18 Mar 2014 13:11:47 +0100	[thread overview]
Message-ID: <53283803.5010209@redhat.com> (raw)
In-Reply-To: <53273309.8060103@zytor.com>

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

  reply	other threads:[~2014-03-18 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 20:01 [PATCH 0/2] KVM: x86 emulator: emulate MOVAPS and MOVAPD SSE instructions Igor Mammedov
2014-03-15 20:01 ` [PATCH 1/2] KVM: x86 emulator: emulate MOVAPS Igor Mammedov
2014-03-15 20:02 ` [PATCH 2/2] KVM: x86 emulator: emulate MOVAPD Igor Mammedov
2014-03-15 22:39 ` [PATCH 0/2] KVM: x86 emulator: emulate MOVAPS and MOVAPD SSE instructions H. Peter Anvin
2014-03-17 11:19   ` Paolo Bonzini
2014-03-15 22:42 ` H. Peter Anvin
2014-03-17  9:30   ` Paolo Bonzini
2014-03-17 15:16     ` H. Peter Anvin
2014-03-17 17:01       ` Paolo Bonzini
2014-03-17 17:38         ` H. Peter Anvin
2014-03-18 12:11           ` Paolo Bonzini [this message]
2014-03-17 11:18 ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53283803.5010209@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@kernel.org \
    --cc=hpa@zytor.com \
    --cc=imammedo@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.