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] [RFC 2/7] target-i386: Introduce compat function to set CPUID 'level'
Date: Fri, 26 Apr 2013 17:16:26 +0200 [thread overview]
Message-ID: <20130426171626.79c383e8@thinkpad> (raw)
In-Reply-To: <1366915386-14728-3-git-send-email-ehabkost@redhat.com>
On Thu, 25 Apr 2013 15:43:01 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> Introduce x86_cpu_compat_set_level(), which can be used by machine-type
> init functions to keep compatibility when CPU models are changed.
Doesn't seems to be used in this series. Why adding dead code, all that should
be replaced by static properties in next release. I plan to respin properties
series shortly after 1.5.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> target-i386/cpu.c | 22 ++++++++++++++++++++++
> target-i386/cpu.h | 1 +
> 2 files changed, 23 insertions(+)
>
> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> index a207474..6ef5842 100644
> --- a/target-i386/cpu.c
> +++ b/target-i386/cpu.c
> @@ -996,6 +996,28 @@ void x86_cpu_compat_set_features(const char *cpu_model, FeatureWord w,
> }
> }
>
> +/**
> + * x86_cpu_compat_set_level:
> + * @cpu_model: CPU model name to be changed. If NULL, all CPU models are changed
> + * @level: New value for 'level' field on CPU model
> + *
> + * Change CPU model 'level' field for compatibility.
> + *
> + * This function may be used by machine-type compatibility functions
> + * to set a backwards-compatible value for the 'level' field on CPU models.
> + */
> +void x86_cpu_compat_set_level(const char *cpu_model, uint32_t level)
> +{
> + x86_def_t *def;
> + int i;
> + for (i = 0; i < ARRAY_SIZE(builtin_x86_defs); i++) {
> + def = &builtin_x86_defs[i];
> + if (!cpu_model || !strcmp(cpu_model, def->name)) {
> + def->level = level;
> + }
> + }
> +}
> +
> #ifdef CONFIG_KVM
> static int cpu_x86_fill_model_id(char *str)
> {
> diff --git a/target-i386/cpu.h b/target-i386/cpu.h
> index 60581e1..86a5988 100644
> --- a/target-i386/cpu.h
> +++ b/target-i386/cpu.h
> @@ -1256,6 +1256,7 @@ void disable_kvm_pv_eoi(void);
>
> void x86_cpu_compat_set_features(const char *cpu_model, FeatureWord w,
> uint32_t feat_add, uint32_t feat_remove);
> +void x86_cpu_compat_set_level(const char *cpu_model, uint32_t level);
>
>
> /* Return name of 32-bit register, from a R_* constant */
> --
> 1.8.1.4
>
>
--
Regards,
Igor
next prev parent reply other threads:[~2013-04-26 15:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 18:42 [Qemu-devel] [RFC 0/7] CPUID fixes for 1.5 Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 1/7] target-i386: Introduce generic CPUID feature compat function Eduardo Habkost
2013-05-06 20:34 ` Andreas Färber
2013-04-25 18:43 ` [Qemu-devel] [RFC 2/7] target-i386: Introduce compat function to set CPUID 'level' Eduardo Habkost
2013-04-26 15:16 ` Igor Mammedov [this message]
2013-04-26 15:28 ` Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 3/7] target-i386: Introduce compat function to set CPUID 'model' Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 4/7] pc: Use separate init functions for pc-*-1.4 Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 5/7] target-i386: n270 can MOVBE Eduardo Habkost
2013-05-06 20:35 ` Andreas Färber
2013-04-25 18:43 ` [Qemu-devel] [RFC 6/7] target-i386: change CPUID model of 486 to 8 Eduardo Habkost
2013-04-25 19:11 ` Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 7/7] target-i386: Disable direct passthrough of PMU CPUID leaf by default Eduardo Habkost
2013-04-26 15:10 ` Igor Mammedov
2013-04-26 15:31 ` Eduardo Habkost
2013-04-26 15:33 ` Andreas Färber
2013-04-26 15:39 ` Igor Mammedov
2013-04-26 17:30 ` Eduardo Habkost
2013-04-26 17:41 ` Igor Mammedov
2013-04-26 19:01 ` Eduardo Habkost
2013-04-30 17:04 ` Igor Mammedov
2013-04-30 19:57 ` Eduardo Habkost
2013-05-01 11:14 ` Andreas Färber
2013-05-02 14:43 ` Eduardo Habkost
2013-05-02 14:50 ` Andreas Färber
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=20130426171626.79c383e8@thinkpad \
--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).