public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: This combination of AMDprocessors is not suitable for SMP?
Date: Thu, 23 Jul 2009 12:34:40 +0200	[thread overview]
Message-ID: <4A683CC0.90509@amd.com> (raw)
In-Reply-To: <4A6816AD.2060700@msgid.tls.msk.ru>

Michael Tokarev wrote:
> (yes there's no typo in $subject, it's an old formatting
> bug in printk).
> 
> When booting kvm guest on an AMD CPU, guest kernel prints
> this warning:
> 
>  WARNING: This combination of AMDprocessors is not suitable for SMP.
> 
> be it SMP or UP guest.  What's wrong with this "combination",
> and can it be fixed?
The qemu64 CPU model KVM injects into the guest lets it see an AMD K7 
with 64bit extension. Only some AMD K7 (Athlon-MP) were certified for 
SMP support, so this code warns the user about an unsupported hardware.
When running KVM you can ignore this warning, as it only applies to 
non-KVM capable processors and has no meaning for virtual SMP anyway.

If you like this warning to disappear, you can use "-cpu host" (and 
probably loose migration capability) or wait for the new safe64 CPU 
type, which will use family 15 instead of 6.

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


      reply	other threads:[~2009-07-23 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  7:52 This combination of AMDprocessors is not suitable for SMP? Michael Tokarev
2009-07-23 10:34 ` Andre Przywara [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=4A683CC0.90509@amd.com \
    --to=andre.przywara@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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