From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: SEP regression in kvm-20?
Date: Mon, 23 Apr 2007 10:17:59 +0300 [thread overview]
Message-ID: <462C5DA7.1040407@qumranet.com> (raw)
In-Reply-To: <1177304168.17026.49.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Rusty Russell wrote:
> Hi all,
>
> I note that Linux under kvm 20 doesn't use sysenter, while it did under
> kvm 19. There's no "sep" in /proc/cpuinfo
x86info does report sep, but arch/i386/kernel/cpu/intel.c has this to say:
/* SEP CPUID bug: Pentium Pro reports SEP but doesn't have it
until model 3 mask 3 */
if ((c->x86<<8 | c->x86_model<<4 | c->x86_mask) < 0x633)
clear_bit(X86_FEATURE_SEP, c->x86_capability);
whereas our cpu is
cpu family : 6
model : 2
so, no SEP for you. I imagine we can bump the model and mask to 3.
> and the vendor id looks kinda
> random too: this looks like a cpuid problem?
>
I see a
vendor_id : GenuineIntel
?
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-23 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 4:56 SEP regression in kvm-20? Rusty Russell
[not found] ` <1177304168.17026.49.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-04-23 7:17 ` Avi Kivity [this message]
[not found] ` <462C5DA7.1040407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-23 11:18 ` Rusty Russell
[not found] ` <1177327093.17026.67.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-04-23 13:15 ` Avi Kivity
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=462C5DA7.1040407@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.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