From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Babu Moger <babu.moger@amd.com>
Cc: pbonzini@redhat.com, rth@twiddle.net, ehabkost@redhat.com,
mtosatti@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org,
pixo@polepetko.eu, Gary.Hook@amd.com
Subject: Re: [Qemu-devel] [PATCH v2 1/5] target/i386: Fix a minor typo found while reviwing
Date: Wed, 28 Feb 2018 18:38:13 +0100 [thread overview]
Message-ID: <20180228173813.GA8418@flask> (raw)
In-Reply-To: <1519439425-27883-2-git-send-email-babu.moger@amd.com>
2018-02-23 21:30-0500, Babu Moger:
> Changed KVM_CPUID_FLAG_SIGNIFCANT_INDEX to KVM_CPUID_FLAG_SIGNIFICANT_INDEX
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
> linux-headers/asm-x86/kvm.h | 2 +-
> target/i386/kvm.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/linux-headers/asm-x86/kvm.h b/linux-headers/asm-x86/kvm.h
> index f3a9604..6aec661 100644
> --- a/linux-headers/asm-x86/kvm.h
> +++ b/linux-headers/asm-x86/kvm.h
> @@ -220,7 +220,7 @@ struct kvm_cpuid_entry2 {
> __u32 padding[3];
> };
>
> -#define KVM_CPUID_FLAG_SIGNIFCANT_INDEX (1 << 0)
The typo is in the original kernel header and we periodically copy it
over with scripts/update-linux-headers.sh, so this change would only add
overhead in the long run.
I'd keep the typo.
(The alternative is to add KVM_CPUID_FLAG_SIGNIFICANT_INDEX to the linux
header, so there would be both variants and use the correct one here.)
Thanks.
> +#define KVM_CPUID_FLAG_SIGNIFICANT_INDEX (1 << 0)
> #define KVM_CPUID_FLAG_STATEFUL_FUNC (1 << 1)
> #define KVM_CPUID_FLAG_STATE_READ_NEXT (1 << 2)
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index ad4b159..85856b6 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -844,7 +844,7 @@ int kvm_arch_init_vcpu(CPUState *cs)
> break;
> }
> c->function = i;
> - c->flags = KVM_CPUID_FLAG_SIGNIFCANT_INDEX;
> + c->flags = KVM_CPUID_FLAG_SIGNIFICANT_INDEX;
> c->index = j;
> cpu_x86_cpuid(env, i, j, &c->eax, &c->ebx, &c->ecx, &c->edx);
>
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2018-02-28 17:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 2:30 [Qemu-devel] [PATCH v2 0/5] Enable TOPOEXT to support hyperthreading on AMD CPU Babu Moger
2018-02-24 2:30 ` [Qemu-devel] [PATCH v2 1/5] target/i386: Fix a minor typo found while reviwing Babu Moger
2018-02-28 17:38 ` Radim Krčmář [this message]
2018-02-28 18:49 ` Eric Blake
2018-02-28 21:20 ` Moger, Babu
2018-02-28 21:12 ` Moger, Babu
2018-02-24 2:30 ` [Qemu-devel] [PATCH v2 2/5] target/i386: Populate AMD Processor Cache Information Babu Moger
2018-02-28 18:08 ` Radim Krčmář
2018-03-01 15:55 ` Moger, Babu
2018-03-01 19:56 ` Radim Krčmář
2018-03-02 16:50 ` Moger, Babu
2018-02-24 2:30 ` [Qemu-devel] [PATCH v2 3/5] target/i386: Add support for CPUID_8000_001E for AMD Babu Moger
2018-02-28 18:24 ` Radim Krčmář
2018-02-28 22:18 ` Moger, Babu
2018-03-01 19:57 ` Radim Krčmář
2018-03-02 16:50 ` Moger, Babu
2018-02-24 2:30 ` [Qemu-devel] [PATCH v2 4/5] target/i386: Enable TOPOEXT feature on AMD EPYC CPU Babu Moger
2018-02-24 2:30 ` [Qemu-devel] [PATCH v2 5/5] target/i386: Remove generic SMT thread check Babu Moger
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=20180228173813.GA8418@flask \
--to=rkrcmar@redhat.com \
--cc=Gary.Hook@amd.com \
--cc=babu.moger@amd.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pixo@polepetko.eu \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).