qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH] don't expose lm bit if kernel is not 64-bit capable.
Date: Tue, 03 Feb 2009 21:37:47 +0200	[thread overview]
Message-ID: <49889D0B.9040404@redhat.com> (raw)
In-Reply-To: <1233673454-14526-1-git-send-email-glommer@redhat.com>

Glauber Costa wrote:
> If the kernel is not 64-bit capable (even if the host
> machine is) do not expose the lm bit in guest cpuid.
>
>
> diff --git a/target-i386/helper.c b/target-i386/helper.c
> index a28ab93..997e4e1 100644
> --- a/target-i386/helper.c
> +++ b/target-i386/helper.c
> @@ -24,6 +24,7 @@
>  #include <inttypes.h>
>  #include <signal.h>
>  #include <assert.h>
> +#include <sys/utsname.h>
>  
>  #include "cpu.h"
>  #include "exec-all.h"
> @@ -1520,13 +1521,16 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index,
>  
>          if (kvm_enabled()) {
>              uint32_t h_eax, h_edx;
> +            struct utsname utsname;
> +
> +            uname(&utsname);
>  

It would be better to use KVM_GET_SUPPORTED_CPUID for this (and 
similar).  uname() can lie, and in theory kvm can support x86_64 on i386 
kernels (although patches to implement this would be rejected on 
cost/benefit and aesthetic concerns).

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  parent reply	other threads:[~2009-02-03 19:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 15:04 [Qemu-devel] [PATCH] don't expose lm bit if kernel is not 64-bit capable Glauber Costa
2009-02-03 15:44 ` Alexander Graf
2009-02-03 15:52   ` Glauber Costa
2009-02-03 17:58     ` Anthony Liguori
2009-02-03 19:35 ` Avi Kivity
2009-02-03 19:37 ` Avi Kivity
2009-02-03 20:00   ` Glauber Costa
2009-02-03 21:14     ` Anthony Liguori
2009-02-03 21:35       ` Glauber Costa
2009-02-03 21:42         ` Anthony Liguori
2009-02-04  8:10       ` Avi Kivity
2009-02-03 19:37 ` Avi Kivity [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-03 20:15 Glauber Costa

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=49889D0B.9040404@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.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).