From: "H. Peter Anvin" <hpa@zytor.com>
To: Paolo Bonzini <pbonzini@redhat.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: Mon, 17 Mar 2014 10:38:17 -0700 [thread overview]
Message-ID: <53273309.8060103@zytor.com> (raw)
In-Reply-To: <53272A53.8090605@redhat.com>
On 03/17/2014 10:01 AM, Paolo Bonzini wrote:
> the emulator).
>
> If CS and possibly SS are valid real mode selectors, it should be
> possible to run big real mode at almost-full speed, taking exits only
> for memory accesses via other segment registers. It is on my todo list,
> but not very high. Depending on the exit overhead, it may be a better
> idea to revert the emulate_invalid_guest_state default to N and let
> people who care about big real mode specify Y.
>
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>.
As Big Real Mode is part of the spec for certain things (option ROMs, as
we discussed) it probably matters, but especially with the CPUs not
supporting unrestricted mode fading into history I suspect it is fine
for BRM to be slow on those older processors.
The PM transitions that you mentioned are usually only a handful of
instructions and thus can be slow.
-hpa
next prev parent reply other threads:[~2014-03-17 17:38 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 [this message]
2014-03-18 12:11 ` Paolo Bonzini
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=53273309.8060103@zytor.com \
--to=hpa@zytor.com \
--cc=gleb@kernel.org \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).