public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Avi Kivity <avi@redhat.com>
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 14:28:02 +0200	[thread overview]
Message-ID: <20100422122802.GA28773@8bytes.org> (raw)
In-Reply-To: <4BD03D5A.6090905@redhat.com>

On Thu, Apr 22, 2010 at 03:13:14PM +0300, Avi Kivity wrote:
> On 04/22/2010 03:02 PM, Joerg Roedel wrote:

>> We can't just take the host-cpuid
>> because most of the additional svm features need special emulation in
>> the kernel. Or do you think this should better be handled in
>> target-i386/cpuid.c?
>>    
>
> 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.

> (need feature names for the bits, too, so you can enable or disable them  
> from the command line)

Yeah, I know. I omitted that for the first bring-up. It was planned for
a later patch.

	Joerg


  reply	other threads:[~2010-04-22 12:28 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 [this message]
2010-04-22 14:48         ` 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=20100422122802.GA28773@8bytes.org \
    --to=joro@8bytes.org \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --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