From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] allow hypervisor CPUID bit to be overriden
Date: Tue, 23 Jun 2009 13:01:16 +0300 [thread overview]
Message-ID: <4A40A7EC.8070100@redhat.com> (raw)
In-Reply-To: <1245707244-743-1-git-send-email-andre.przywara@amd.com>
On 06/23/2009 12:47 AM, Andre Przywara wrote:
> KVM defaults to the hypervisor CPUID bit to be set, whereas pure QEMU clears
> it. On some occasions one want to set or clear it the other way round (for
> instance to get HyperV running inside a guest).
> Allow the default to be overridden on the command line and fix some
> whitespace damage on the way.
>
It makes sense for qemu to set the hypervisor bit unconditionally. A
guest running under qemu is not bare metal.
That's a separate change though. Patch looks good.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 1/2] allow hypervisor CPUID bit to be overriden
Date: Tue, 23 Jun 2009 13:01:16 +0300 [thread overview]
Message-ID: <4A40A7EC.8070100@redhat.com> (raw)
In-Reply-To: <1245707244-743-1-git-send-email-andre.przywara@amd.com>
On 06/23/2009 12:47 AM, Andre Przywara wrote:
> KVM defaults to the hypervisor CPUID bit to be set, whereas pure QEMU clears
> it. On some occasions one want to set or clear it the other way round (for
> instance to get HyperV running inside a guest).
> Allow the default to be overridden on the command line and fix some
> whitespace damage on the way.
>
It makes sense for qemu to set the hypervisor bit unconditionally. A
guest running under qemu is not bare metal.
That's a separate change though. Patch looks good.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-23 10:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 21:47 [PATCH 1/2] allow hypervisor CPUID bit to be overriden Andre Przywara
2009-06-22 21:47 ` [Qemu-devel] " Andre Przywara
2009-06-23 10:01 ` Avi Kivity [this message]
2009-06-23 10:01 ` [Qemu-devel] " Avi Kivity
2009-06-23 11:31 ` Paul Brook
2009-06-23 11:31 ` Paul Brook
2009-06-23 11:35 ` Avi Kivity
2009-06-23 11:35 ` Avi Kivity
2009-06-23 11:43 ` Paul Brook
2009-06-23 11:43 ` Paul Brook
2009-06-24 21:20 ` Jamie Lokier
2009-06-24 21:20 ` Jamie Lokier
2009-06-25 5:23 ` Gleb Natapov
2009-06-25 5:23 ` Gleb Natapov
2009-06-23 12:37 ` [PATCH 1/2 v2] " Andre Przywara
2009-06-23 12:37 ` [Qemu-devel] " Andre Przywara
2009-06-23 14:17 ` Anthony Liguori
2009-06-23 14:17 ` [Qemu-devel] " Anthony Liguori
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=4A40A7EC.8070100@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=andre.przywara@amd.com \
--cc=kvm@vger.kernel.org \
--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 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.