[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <531A164B.8040402@linux.intel.com>
Date: Fri, 07 Mar 2014 10:56:11 -0800
From: "H. Peter Anvin" <hpa@...ux.intel.com>
To: Fengguang Wu <fengguang.wu@...el.com>
CC: Andreas Herrmann <andreas.herrmann3@....com>,
Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
Yinghai Lu <yhlu.kernel@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [qemu64,+smep,+smap] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/cpu/amd.c:220
init_amd()
On 03/06/2014 09:50 PM, Fengguang Wu wrote:
>>
>> Unfortunately these things are hard to fix in Qemu.
>
> OK. As an alternative, is it possible to pass one of the below CPUID flags in
> the Qemu command line, so as to quiet the warning?
>
I don't see the AMD SMP CPUID flag in there.
Boris, could you help? The problem is that "qemu -cpu
qemu64,+smep,+smap" identifies as an AMD CPU which triggers a
warning/taint because the SMP flag isn't set.
>
> Recognized CPUID flags:
> pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc pse de vme fpu
> hypervisor rdrand f16c avx osxsave xsave aes tsc-deadline popcnt movbe x2apic sse4.2|sse4_2 sse4.1|sse4_1 dca pcid pdcm xtpr cx16 fma cid ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmulqdq|pclmuldq pni|sse3
> smap adx rdseed rtm invpcid erms bmi2 smep avx2 hle bmi1 fsgsbase
> 3dnow 3dnowext lm|i64 rdtscp pdpe1gb fxsr_opt|ffxsr mmxext nx|xd syscall
> perfctr_nb perfctr_core topoext tbm nodeid_msr tce fma4 lwp wdt skinit xop ibs osvw 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm cmp_legacy lahf_lm
> pmm-en pmm phe-en phe ace2-en ace2 xcrypt-en xcrypt xstore-en xstore
> kvm_pv_eoi kvm_steal_time kvm_asyncpf kvmclock kvm_mmu kvm_nopiodelay kvmclock
> pfthreshold pause_filter decodeassists flushbyasid vmcb_clean tsc_scale nrip_save svm_lock lbrv npt
>
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists