From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
Anthony Liguori <anthony@codemonkey.ws>,
kvm@vger.kernel.org
Subject: Re: [PATCH] qemu-kvm: Ask kernel about supported svm features
Date: Thu, 22 Apr 2010 17:48:46 +0300 [thread overview]
Message-ID: <4BD061CE.4060808@redhat.com> (raw)
In-Reply-To: <20100422122802.GA28773@8bytes.org>
On 04/22/2010 03:28 PM, Joerg Roedel wrote:
>
>> Yes. -cpu host should take KVM_GET_SUPPORTED_CPUID output and loop it
>> back to the vcpu configuration, others just take the qemu configuration,
>> mask it with supported bits, and pass it back (see
>> check_features_against_host()).
>>
> Hmm, the plan was to enable with -enable-nesting all kernel supported
> svm features for the guest (and add switches later to remove them
> individually)
> If we activate nested svm with -cpu host in the future thats fine too
> (closed-source hypervisors need that anyway). But we should also define
> a cpu model in which we can migrate nested hypervisors between machines
> were the cpu is not completly indentical.
>
You can use -cpu host, or -cpu kvm64,+svm,+npt,+other_feature... just as
with all other features.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-04-22 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 10:57 [PATCH] qemu-kvm: Ask kernel about supported svm features Joerg Roedel
2010-04-22 11:07 ` Avi Kivity
2010-04-22 12:02 ` Joerg Roedel
2010-04-22 12:13 ` Avi Kivity
2010-04-22 12:28 ` Joerg Roedel
2010-04-22 14:48 ` Avi Kivity [this message]
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=4BD061CE.4060808@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.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