From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, joerg.roedel@amd.com
Subject: Re: [PATCH] Don't try to mess with CPUID when running nested SVM
Date: Fri, 15 May 2009 14:19:50 +0300 [thread overview]
Message-ID: <4A0D4FD6.3040409@redhat.com> (raw)
In-Reply-To: <69F72470-DF44-4BE1-87AF-9FEFF54B69E0@suse.de>
Alexander Graf wrote:
>>> When using nested SVM we usually want the guest to see the exact
>>> CPUID values
>>> we gave it and not some mangled ones.
>>>
>>
>> That would triggered by -cpu host, not nesting.
>
> Oh we have -cpu host already?
No, we don't :)
> hm - treating the hypervisor bit like any other cpuid bit sounds like
> a good idea. I'm wondering though which way should be preferred. I
> usually don't want to have the hypervisor bit set - but maybe I'm the
> minority.
>
Windows requires the hypervisor bit to set in order to pass some testing
program.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2009-05-15 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 9:01 [PATCH] Add external-module-compat header for MSR_VM_IGNNE Alexander Graf
2009-05-15 9:01 ` [PATCH] Don't try to mess with CPUID when running nested SVM Alexander Graf
2009-05-15 11:09 ` Avi Kivity
2009-05-15 11:15 ` Alexander Graf
2009-05-15 11:19 ` 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=4A0D4FD6.3040409@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.