From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [qom-cpu PATCH 1/7] target-i386: Move cpuid_xlevel, cpuid_xlevel2 fields in X86CPU
Date: Tue, 16 Apr 2013 16:17:49 +0200 [thread overview]
Message-ID: <20130416161749.58f64aa4@nial.usersys.redhat.com> (raw)
In-Reply-To: <1366053940-9401-2-git-send-email-ehabkost@redhat.com>
On Mon, 15 Apr 2013 16:25:34 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> As the cpuid_*_features fields will be replaced by an array, put the
> level/xlevel/xlevel2 fields together in the struct, as they won't be
> close to the corresponding cpuid_*_features fields anymore.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> target-i386/cpu.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target-i386/cpu.h b/target-i386/cpu.h
> index cf1b05c..500fe93 100644
> --- a/target-i386/cpu.h
> +++ b/target-i386/cpu.h
> @@ -835,19 +835,19 @@ typedef struct CPUX86State {
>
> /* processor features (e.g. for CPUID insn) */
> uint32_t cpuid_level;
> + uint32_t cpuid_xlevel;
> + uint32_t cpuid_xlevel2;
> uint32_t cpuid_vendor1;
> uint32_t cpuid_vendor2;
> uint32_t cpuid_vendor3;
> uint32_t cpuid_version;
> uint32_t cpuid_features;
> uint32_t cpuid_ext_features;
> - uint32_t cpuid_xlevel;
> uint32_t cpuid_model[12];
> uint32_t cpuid_ext2_features;
> uint32_t cpuid_ext3_features;
> uint32_t cpuid_apic_id;
> /* Store the results of Centaur's CPUID instructions */
> - uint32_t cpuid_xlevel2;
> uint32_t cpuid_ext4_features;
> /* Flags from CPUID[EAX=7,ECX=0].EBX */
> uint32_t cpuid_7_0_ebx_features;
Reviewed-By: Igor Mammedov <imammedo@redhat.com>
next prev parent reply other threads:[~2013-04-16 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 19:25 [Qemu-devel] [qom-cpu PATCH 0/7] replace cpuid_*features fields with a featue word array (v8) Eduardo Habkost
2013-04-15 19:25 ` [Qemu-devel] [qom-cpu PATCH 1/7] target-i386: Move cpuid_xlevel, cpuid_xlevel2 fields in X86CPU Eduardo Habkost
2013-04-16 14:17 ` Igor Mammedov [this message]
2013-04-15 19:25 ` [Qemu-devel] [qom-cpu PATCH 2/7] target-i386/kvm.c: Code formatting changes Eduardo Habkost
2013-04-16 14:23 ` Igor Mammedov
2013-04-16 14:35 ` Eduardo Habkost
2013-04-15 19:25 ` [Qemu-devel] [qom-cpu PATCH 3/7] target-i386: Move xlevel/xlevel2 in struct x86_def_t Eduardo Habkost
2013-04-16 14:32 ` Igor Mammedov
2013-04-16 14:41 ` Eduardo Habkost
2013-04-15 19:25 ` [Qemu-devel] [qom-cpu PATCH 4/7] target-i386/cpu.c: Break lines on kvm_cpu_fill_host() Eduardo Habkost
2013-04-16 15:18 ` Igor Mammedov
2013-04-16 15:43 ` Eduardo Habkost
2013-04-15 19:25 ` [Qemu-devel] [qom-cpu PATCH 5/7] target-i386/cpu.c: Break lines on kvm_check_features_against_host() Eduardo Habkost
2013-04-15 19:25 ` [Qemu-devel] [qom-cpu PATCH 6/7] target-i386/cpu.c: Break lines on builtin_x86_defs array Eduardo Habkost
2013-04-15 19:25 ` [Qemu-devel] [qom-cpu PATCH 7/7] target-i386: Replace cpuid_*features fields with a feature word array Eduardo Habkost
2013-04-16 15:45 ` Igor Mammedov
2013-04-16 15:51 ` [Qemu-devel] [qom-cpu PATCH 0/7] replace cpuid_*features fields with a featue word array (v8) Eduardo Habkost
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=20130416161749.58f64aa4@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--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).