From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Dave Jones <davej@redhat.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
Yinghai Lu <yhlu.kernel@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [qemu64,+smep,+smap] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/cpu/amd.c:220 init_amd()
Date: Fri, 07 Mar 2014 13:01:22 -0800 [thread overview]
Message-ID: <531A33A2.5030706@linux.intel.com> (raw)
In-Reply-To: <20140307191050.GA10961@redhat.com>
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
next prev parent reply other threads:[~2014-03-07 21:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 1:58 Fengguang Wu
2014-03-07 5:03 ` H. Peter Anvin
2014-03-07 5:50 ` Fengguang Wu
2014-03-07 18:56 ` H. Peter Anvin
2014-03-07 19:10 ` Dave Jones
2014-03-07 21:01 ` H. Peter Anvin [this message]
2014-03-07 21:38 ` Borislav Petkov
2014-03-07 22:06 ` Dave Jones
2014-03-07 22:11 ` H. Peter Anvin
2014-03-07 22:22 ` Dave Jones
2014-03-07 22:27 ` Fengguang Wu
2014-03-07 22:34 ` Borislav Petkov
2014-03-07 22:20 ` Borislav Petkov
2014-03-07 22:27 ` Dave Jones
2014-03-07 22:39 ` Borislav Petkov
2014-03-09 18:07 ` Paolo Bonzini
2014-03-09 18:50 ` Borislav Petkov
2014-03-10 0:01 ` H. Peter Anvin
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=531A33A2.5030706@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=andreas.herrmann3@amd.com \
--cc=bp@alien8.de \
--cc=davej@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=yhlu.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome