From: Igor Mammedov <imammedo@redhat.com>
To: Don Slutz <Don@cloudswitch.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
kvm@vger.kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org,
avi@redhat.com, anthony@codemonkey.ws, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v4 02/17] target-i386: Add missing kvm bits.
Date: Fri, 21 Sep 2012 10:39:52 +0200 [thread overview]
Message-ID: <20120921103952.34c176c7@thinkpad.mammed.net> (raw)
In-Reply-To: <1348171412-23669-3-git-send-email-Don@CloudSwitch.com>
On Thu, 20 Sep 2012 16:03:17 -0400
Don Slutz <Don@cloudswitch.com> wrote:
> Fix duplicate name (kvmclock => kvm_clock2) also.
>
> Signed-off-by: Don Slutz <Don@CloudSwitch.com>
> ---
> target-i386/cpu.c | 12 ++++++++----
> 1 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> index 0313cf5..5f9866a 100644
> --- a/target-i386/cpu.c
> +++ b/target-i386/cpu.c
> @@ -87,10 +87,14 @@ static const char *ext3_feature_name[] = {
> };
>
> static const char *kvm_feature_name[] = {
> - "kvmclock", "kvm_nopiodelay", "kvm_mmu", "kvmclock", "kvm_asyncpf", NULL, "kvm_pv_eoi", NULL,
> - NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
> - NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
> - NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
> + "kvmclock", "kvm_nopiodelay", "kvm_mmu", "kvm_clock2",
before patch if "kvmclock" is specified it would set 0 and 3 bits,
after patch only bit 0 is set.
Is it correct/expected behavior? if yes, please add rationale into patch
description.
> + "kvm_asyncpf", "kvm_steal_time", "kvm_pv_eoi", NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + "kvm_clock_stable", NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> };
>
> static const char *svm_feature_name[] = {
> --
> 1.7.1
>
--
Regards,
Igor
next prev parent reply other threads:[~2012-09-21 8:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 20:03 [Qemu-devel] [PATCH v4 00/17] Allow changing of Hypervisor CPUIDs Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 01/17] target-i386: Allow tsc-frequency to be larger then 2.147G Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 02/17] target-i386: Add missing kvm bits Don Slutz
2012-09-21 8:39 ` Igor Mammedov [this message]
2012-09-21 12:36 ` Eduardo Habkost
2012-09-21 13:17 ` Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 03/17] target-i386: Add Hypervisor level Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 04/17] target-i386: Add cpu object access routines for " Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 05/17] target-i386: Add x86_set_hyperv Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 06/17] target-i386: Use Hypervisor level in -machine pc, accel=kvm Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 07/17] target-i386: Use Hypervisor level in -machine pc, accel=tcg Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 08/17] target-i386: Add Hypervisor vendor Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 09/17] target-i386: Add cpu object access routines for " Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 10/17] target-i386: Use Hypervisor vendor in -machine pc, accel=kvm Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 11/17] target-i386: Use Hypervisor vendor in -machine pc, accel=tcg Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 12/17] target-i386: Add some known names to Hypervisor vendor Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 13/17] target-i386: Add optional Hypervisor leaf extra Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 14/17] target-i386: Add cpu object access routines for " Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 15/17] target-i386: Add setting of Hypervisor leaf extra for known vmare4 Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 16/17] target-i386: Use Hypervisor leaf extra in -machine pc, accel=kvm Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 17/17] target-i386: Use Hypervisor leaf extra in -machine pc, accel=tcg Don Slutz
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=20120921103952.34c176c7@thinkpad.mammed.net \
--to=imammedo@redhat.com \
--cc=Don@cloudswitch.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.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 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).