qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] kvm: also fill 0x40000000 (vmm) cpuid leafes.
Date: Tue, 11 Nov 2008 15:03:34 -0600	[thread overview]
Message-ID: <4919F326.4070902@codemonkey.ws> (raw)
In-Reply-To: <49140DEE.7070000@redhat.com>

Gerd Hoffmann wrote:
>   Hi,
>
> $subject says all, patch attached.
>   

It really doesn't :-)

0x4000xxxx are the virtualization leaves, that we don't set so there is 
no functional change from this patch.  The KVM PV ABI doesn't use eax as 
the max CPUID leaf of 0x40000000 so that's at least one example of them 
not behaving like this.

So can you be a lot more specific about how you intend on using these 
leaves?

Regards,

Anthony Liguori

> please apply,
>   Gerd
>   

  reply	other threads:[~2008-11-11 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  9:44 [Qemu-devel] [patch] kvm: also fill 0x40000000 (vmm) cpuid leafes Gerd Hoffmann
2008-11-11 21:03 ` Anthony Liguori [this message]
2008-11-11 21:30   ` Gerd Hoffmann

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=4919F326.4070902@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).