From: "Nadav Har'El" <nyh@math.technion.ac.il>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Add VMX cpuid feature to qemu64
Date: Wed, 5 Jan 2011 10:17:37 +0200 [thread overview]
Message-ID: <20110105081737.GA23681@fermat.math.technion.ac.il> (raw)
In-Reply-To: <50D01580-FB08-459A-84B9-7C8AA8190AFD@suse.de>
On Tue, Jan 04, 2011, Alexander Graf wrote about "Re: [Qemu-devel] [PATCH] Add VMX cpuid feature to qemu64":
> If qemu-kvm still uses the "qemu64" type, that's plainly a bug :). It really should use -cpu kvm64 / kvm32 as default.
When I run qemu-kvm's qemu-system-x86_64, and look at the CPU I get in the
guest, I the CPU is clearly "QEMU Virtual CPU version 0.13.50" (qemu64) and
not "Common KVM processor" (kvm64) the "-enable-kvm" option doesn't appear to
change anything. Could this have always been a bug, which remained hidden
in plain sight? :-)
If I send a patch to default to kvm64, not qemu64, when KVM is being used,
would that be acceptable by all parties involved (KVM people and QEMU people)?
Also, kvm64 appears to have much fewer capabilities listed than qemu64.
Was this list ever kept up to date with KVM's capabilities? On first glance
it appars that even CPUID_EXT3_SVM is missing, so if kvm64 is used I think
nested SVM will also stop working (in my patch, I can add this bit just like
I plan to add CPUID_EXT_VMX).
> > Well, as you can see in target-i386/cpuid.c, at least in the qemu version
> > I checked out from KVM's repository, the "core2duo" and "coreduo" cpu types
> > do list the CPUID_EXT_VMX - and those are the only ones that list this feature.
>
> Oops, probably my bad :).
Do you want me to fix that in the patch as well?
Thanks,
Nadav.
> If you add CPUID_EXT_VMX to the "kvm64" type and make that the default when kvm is enabled (like we did for nested svm), all should be well, no?
I don't know, I don't know how the KVM users would react to their default
CPU type being changed from qemu64 to kvm64. Perhaps Avi Kivity or somebody
else has an opinion about this?
Thanks,
Nadav.
--
Nadav Har'El | Wednesday, Jan 5 2011, 29 Tevet 5771
nyh@math.technion.ac.il |-----------------------------------------
Phone +972-523-790466, ICQ 13349191 |Those who beat their swords into
http://nadav.harel.org.il |plowshares will plow for those who don't.
next prev parent reply other threads:[~2011-01-05 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 15:06 [Qemu-devel] [PATCH] Add VMX cpuid feature to qemu64 Nadav Har'El
2011-01-04 15:53 ` Alexander Graf
2011-01-04 21:39 ` Nadav Har'El
2011-01-04 21:55 ` Alexander Graf
2011-01-05 8:17 ` Nadav Har'El [this message]
2011-01-05 8:32 ` Avi Kivity
2011-01-05 8:50 ` Nadav Har'El
2011-01-05 9:06 ` Avi Kivity
2011-01-05 9:22 ` Nadav Har'El
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=20110105081737.GA23681@fermat.math.technion.ac.il \
--to=nyh@math.technion.ac.il \
--cc=agraf@suse.de \
--cc=avi@redhat.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).