[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <531A33A2.5030706@linux.intel.com>
Date: Fri, 07 Mar 2014 13:01:22 -0800
From: "H. Peter Anvin" <hpa@...ux.intel.com>
To: Dave Jones <davej@...hat.com>,
Fengguang Wu <fengguang.wu@...el.com>,
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/07/2014 11:10 AM, Dave Jones wrote:
> On Fri, Mar 07, 2014 at 10:56:11AM -0800, H. Peter Anvin wrote:
> > 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.
>
> qemu64 triggers this ? That spew comes from amd_k7_smp_check()
> which should only run on family 6, which was all 32bit.
>
[ 0.152749] smpboot: CPU0: AMD QEMU Virtual CPU version 1.6.0 (fam:
06, model: 02, stepping: 03)
Seems they are using a really odd CPUID combination, then.
-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