All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Use host CPUID processor info
Date: Sun, 08 Jul 2007 11:09:41 +0300	[thread overview]
Message-ID: <46909BC5.1040505@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A01B8F3FB-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

Dong, Eddie wrote:
> Use host cpu model name, type, family, Model, stepping for guest.
>
> Against head.
>
>   

This is turning into a mix of the qemu cpuid and the host cpuid.  We 
need to think of a way to make this controllable.


> Signed-off-by: Yaozu (Eddie) Dong <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
> diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
> index bacdb37..1b86a13 100644
> --- a/qemu/qemu-kvm.c
> +++ b/qemu/qemu-kvm.c
> @@ -756,6 +755,10 @@ static void do_cpuid_ent(struct kvm_cpuid_entry *e,
> uint32_t function)
>         if ((h_edx & 0x00100000) == 0)
>             e->edx &= ~0x00100000u;
>      }
> +    if (function == 0x80000002 || function == 0x80000003
> +       || function == 0x80000004) {
> +       host_cpuid(function, &e->eax, &e->ebx, &e->ecx, &e->edx);
> +    }
>      // sysenter isn't supported on compatibility mode on AMD.  and
> syscall
>      // isn't supported in compatibility mode on Intel.  so advertise
> the
>      // actuall cpu, and say goodbye to migration between different
> vendors
> @@ -768,6 +771,9 @@ static void do_cpuid_ent(struct kvm_cpuid_entry *e,
> uint32_t function)
>         e->ecx = bcd[1];
>         e->edx = bcd[2];
>      }
> +    if (function == 0x1) {
> +       host_cpuid(function, &e->eax, NULL, NULL, NULL);
> +    }
>  }
>
>  int kvm_qemu_init_env(CPUState *cenv)
>   


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

  parent reply	other threads:[~2007-07-08  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-07  6:47 Use host CPUID processor info Dong, Eddie
     [not found] ` <10EA09EFD8728347A513008B6B0DA77A01B8F3FB-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-08  8:09   ` Avi Kivity [this message]
     [not found]     ` <46909BC5.1040505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-08 13:45       ` Dong, Eddie
     [not found]         ` <10EA09EFD8728347A513008B6B0DA77A01B8F4A3-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-08 13:49           ` Avi Kivity
     [not found]             ` <4690EB75.1030702-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-08 14:07               ` Dong, Eddie
     [not found]                 ` <10EA09EFD8728347A513008B6B0DA77A01B8F4B3-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-08 15:12                   ` 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=46909BC5.1040505@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@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 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.