All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>,
	Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Borislav Petkov <borislav.petkov@amd.com>,
	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: Thu, 06 Mar 2014 21:03:50 -0800	[thread overview]
Message-ID: <53195336.9080606@linux.intel.com> (raw)
In-Reply-To: <20140307015833.GA10048@localhost>

On 03/06/2014 05:58 PM, Fengguang Wu wrote:
> Hi all,
> 
> I find the below WARNING shows up only in
> 
>         qemu-system-x86_64 -cpu qemu64,+smep,+smap
> 

Yes, it is because Qemu doesn't show the AMD-specific SMP CPUID bit.
It's harmless in that sense.

Unfortunately these things are hard to fix in Qemu.

	-hpa


  reply	other threads:[~2014-03-07  5:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  1:58 [qemu64,+smep,+smap] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/cpu/amd.c:220 init_amd() Fengguang Wu
2014-03-07  5:03 ` H. Peter Anvin [this message]
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
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=53195336.9080606@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=andreas.herrmann3@amd.com \
    --cc=borislav.petkov@amd.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.