From: Paolo Bonzini <pbonzini@redhat.com>
To: Wei Huang <wei@redhat.com>, qemu-devel@nongnu.org
Cc: afaerber@suse.de, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH] target-i386: warns users when CPU threads>1 for AMD CPUs
Date: Tue, 21 Oct 2014 17:47:54 +0200 [thread overview]
Message-ID: <5446802A.20400@redhat.com> (raw)
In-Reply-To: <1413903645-12035-1-git-send-email-wei@redhat.com>
On 10/21/2014 05:00 PM, Wei Huang wrote:
> No AMD CPUs support hyperthreading. When users select threads>1 in
> -smp option, QEMU fixes it by adjusting CPUID_0000_0001_EBX and
> CPUID_8000_0008_ECX based on inputs (sockets, cores, threads);
> so guest VM can boot correctly. However it is still better to gives
> users a warning when such case happens.
>
> Signed-off-by: Wei Huang <wei@redhat.com>
Tweaked as suggested by Eduardo, and applied.
Paolo
> ---
> target-i386/cpu.c | 23 ++++++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> index e7bf9de..84cbbcd 100644
> --- a/target-i386/cpu.c
> +++ b/target-i386/cpu.c
> @@ -2696,6 +2696,10 @@ static void x86_cpu_apic_realize(X86CPU *cpu, Error **errp)
> }
> #endif
>
> +
> +#define IS_AMD_CPU(env) ((env)->cpuid_vendor1 == CPUID_VENDOR_AMD_1 && \
> + (env)->cpuid_vendor2 == CPUID_VENDOR_AMD_2 && \
> + (env)->cpuid_vendor3 == CPUID_VENDOR_AMD_3)
> static void x86_cpu_realizefn(DeviceState *dev, Error **errp)
> {
> CPUState *cs = CPU(dev);
> @@ -2703,6 +2707,7 @@ static void x86_cpu_realizefn(DeviceState *dev, Error **errp)
> X86CPUClass *xcc = X86_CPU_GET_CLASS(dev);
> CPUX86State *env = &cpu->env;
> Error *local_err = NULL;
> + static bool ht_warned;
>
> if (env->features[FEAT_7_0_EBX] && env->cpuid_level < 7) {
> env->cpuid_level = 7;
> @@ -2711,9 +2716,7 @@ static void x86_cpu_realizefn(DeviceState *dev, Error **errp)
> /* On AMD CPUs, some CPUID[8000_0001].EDX bits must match the bits on
> * CPUID[1].EDX.
> */
> - if (env->cpuid_vendor1 == CPUID_VENDOR_AMD_1 &&
> - env->cpuid_vendor2 == CPUID_VENDOR_AMD_2 &&
> - env->cpuid_vendor3 == CPUID_VENDOR_AMD_3) {
> + if (IS_AMD_CPU(env)) {
> env->features[FEAT_8000_0001_EDX] &= ~CPUID_EXT2_AMD_ALIASES;
> env->features[FEAT_8000_0001_EDX] |= (env->features[FEAT_1_EDX]
> & CPUID_EXT2_AMD_ALIASES);
> @@ -2742,6 +2745,20 @@ static void x86_cpu_realizefn(DeviceState *dev, Error **errp)
> mce_init(cpu);
> qemu_init_vcpu(cs);
>
> + /* AMD CPU doesn't support hyperthreading. Even though QEMU fixes
> + * this issue by adjusting CPUID_0000_0001_EBX and CPUID_8000_0008_ECX
> + * based on inputs (sockets,cores,threads), it is still better to gives
> + * users a warning.
> + *
> + * NOTE: the following code has to follow qemu_init_vcpu(). Otherwise
> + * cs->nr_threads hasn't be populated yet and the checking is incorrect.
> + */
> + if (IS_AMD_CPU(env) && (cs->nr_threads > 1) && !ht_warned) {
> + error_report("AMD CPU doesn't support hyperthreading. Please configure"
> + " -smp options properly.");
> + ht_warned = true;
> + }
> +
> x86_cpu_apic_realize(cpu, &local_err);
> if (local_err != NULL) {
> goto out;
>
prev parent reply other threads:[~2014-10-21 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 15:00 [Qemu-devel] [PATCH] target-i386: warns users when CPU threads>1 for AMD CPUs Wei Huang
2014-10-21 15:37 ` Eduardo Habkost
2014-10-21 15:47 ` Paolo Bonzini [this message]
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=5446802A.20400@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.com \
/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.