From: Andrea Arcangeli <aarcange@redhat.com>
To: Filip Navara <filip.navara@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] allow sysenter on 32bit guests running on vmx host
Date: Wed, 24 Jun 2009 23:13:58 +0200 [thread overview]
Message-ID: <20090624211358.GE15263@random.random> (raw)
In-Reply-To: <5b31733c0906241048m2bb9cb72wdc3d8c0e316611f3@mail.gmail.com>
On Wed, Jun 24, 2009 at 07:48:55PM +0200, Filip Navara wrote:
> On Wed, Jun 24, 2009 at 7:29 PM, Jamie Lokier <jamie@shareable.org> wrote:
> [snip]
> >
> > > Fix is to set model = 3 so it'll be the duron cpu when kvm runs on
> > > amd bare metal (not anymore athlon but userland doesn't see the
> > > difference) and it'll be PII that has sysenter functional like all
> > > cpus that run KVM have too when on intel bare metal.
> >
> > But the vendor id is AMD not Intel in this structure, and the PPro
> > workaround is Intel-only.
> >
> > I've checked Linux kernel code, and it only disables the sep feature
> > if the vendor is GenuineIntel, on old and current kernels.
> >
> > So your patch should make no difference to Linux guests. Did you
> > check Linux behaviour? Does Windows ignore the vendor id?
>
>
> No, it doesn't ignore the vendor, at least not on NT 5.2 (Windows Server
> 2003) and newer kernels. I'm pretty sure it wasn't ignored even in Windows
> XP, older systems didn't implement it.
Correct, not only windows, skype also doesn't ignore the vendor and
it doesn't attempt to run sysenter if running KVM on amd host (or qemu
in any amd/intel host).
skype crashes because windows on intel ignores sep on 6/2/3 (as well
as linux too) and it disables sysenter, but skype runs sysenter in its
binary even on 6/2/3 (tracked with windbg).
next prev parent reply other threads:[~2009-06-24 21:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 16:21 [Qemu-devel] allow sysenter on 32bit guests running on vmx host Andrea Arcangeli
2009-06-24 17:29 ` Jamie Lokier
2009-06-24 17:48 ` Filip Navara
2009-06-24 21:13 ` Andrea Arcangeli [this message]
2009-06-24 21:12 ` Andrea Arcangeli
2009-06-24 21:39 ` Jamie Lokier
2009-06-24 22:32 ` Andrea Arcangeli
2009-06-25 8:11 ` [Qemu-devel] KVMs default CPU type (was: allow sysenter on 32bit guests running on vmx host) Andre Przywara
2009-06-25 8:29 ` [Qemu-devel] KVMs default CPU type Avi Kivity
2009-06-26 0:42 ` [Qemu-devel] KVMs default CPU type (was: allow sysenter on 32bit guests running on vmx host) Andrea Arcangeli
2009-06-26 1:06 ` Andrea Arcangeli
2009-06-25 17:39 ` [Qemu-devel] allow sysenter on 32bit guests running on vmx host Paul Brook
2009-06-25 21:02 ` Andrea Arcangeli
2009-06-25 22:12 ` Paul Brook
2009-06-25 23:27 ` Andrea Arcangeli
2009-06-25 23:49 ` Paul Brook
2009-06-26 0:06 ` Andrea Arcangeli
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=20090624211358.GE15263@random.random \
--to=aarcange@redhat.com \
--cc=filip.navara@gmail.com \
--cc=qemu-devel@nongnu.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).