public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: CPUID emulation
Date: Thu, 31 May 2007 04:58:41 -0700	[thread overview]
Message-ID: <20070531115841.GG22798@frankl.hpl.hp.com> (raw)
In-Reply-To: <465EB6E5.7000000-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi,

On Thu, May 31, 2007 at 02:52:05PM +0300, Avi Kivity wrote:
> Stephane Eranian wrote:
> >>
> >>If the guest cpuid is set to a least common denominator, it should work.
> >>
> >>    
> >There is no common denominator between a P4 and Intel Core 2 Duo for the
> >performance counters. So you cannot simply use a generic member of family
> >15 to fake the guest cpuid runnning on Intel Core 2 Duo host.
> >
> >  
> 
> So, the performance counter functionality will not be available if you 
> have a mixed server farm with these processors.
> 
That's like what is going to happen.

> If applications use model version to detect performance counters, and 
> not cpuid bits, then there is no way to prevent guests using performance 
> counters.  Fortunately this is limited to specialized applications.
> 
They use cpuid. I expect more and more applications/OS will rely on
performance counters to boost performance at runtime.

-- 
-Stephane

-------------------------------------------------------------------------
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/

  parent reply	other threads:[~2007-05-31 11:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31  8:20 CPUID emulation Stephane Eranian
     [not found] ` <20070531082006.GB22798-HU54gidqsKnWxDs0y9d3MAC/G2K4zDHf@public.gmane.org>
2007-05-31  8:39   ` Avi Kivity
     [not found]     ` <465E89A8.9020201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-31 11:29       ` Stephane Eranian
     [not found]         ` <20070531112906.GC22798-HU54gidqsKnWxDs0y9d3MAC/G2K4zDHf@public.gmane.org>
2007-05-31 11:35           ` Avi Kivity
     [not found]             ` <465EB310.7080402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-31 11:44               ` Stephane Eranian
     [not found]                 ` <20070531114447.GF22798-HU54gidqsKnWxDs0y9d3MAC/G2K4zDHf@public.gmane.org>
2007-05-31 11:52                   ` Avi Kivity
     [not found]                     ` <465EB6E5.7000000-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-31 11:58                       ` Stephane Eranian [this message]
     [not found]                         ` <20070531115841.GG22798-HU54gidqsKnWxDs0y9d3MAC/G2K4zDHf@public.gmane.org>
2007-05-31 15:12                           ` Troy Benjegerdes
     [not found]                             ` <20070531151244.GC6474-na1kE3HDu0idQnJuSAr7PQ@public.gmane.org>
2007-05-31 15:38                               ` ron minnich
2007-05-31 18:30                           ` Ulrich Drepper
     [not found]                             ` <465F145F.5040003-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-06-01  1:12                               ` H. Peter Anvin

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=20070531115841.GG22798@frankl.hpl.hp.com \
    --to=eranian-sdzt885ts8hqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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