mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yinghai@kernel.org>
To: "Yan Li" <elliot.li.tech@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	joerg.roedel@amd.com, rjmaomao@gmail.com,
	"Thomas Gleixner" <tglx@linutronix.de>,
	nancydreaming@gmail.com
Subject: Re: [PATCH 2/2] Suppress false "mtrr all empty" warning message when running as VMware guest
Date: Wed, 24 Sep 2008 09:39:20 -0700	[thread overview]
Message-ID: <86802c440809240939h63b14efdm1382ffe4c44c6660@mail.gmail.com> (raw)
In-Reply-To: <48da36b3.0e0d6e0a.1c8e.fffff980@mx.google.com>

On Wed, Sep 24, 2008 at 5:24 AM, Yan Li <elliot.li.tech@gmail.com> wrote:
> Since the mtrr empty was detected very early before we can use DMI or
> PCI to check whether we are running as a VMware guest or not, we now
> only print an info there. Warning will only be issued later when we
> are sure that we are not running as a VMware guest.
>
> mtrr_trim_uncached_memory() is modified to return meaningful codes for
> later warning decision.

we have moved dmi_scan_machine() much early...

so please check with latest tip/master to use
dmi_check_system with that.

BTW:
those warning should be good, because VMware is the root cause.

YH

  parent reply	other threads:[~2008-09-24 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a120cfa37281607d8dc361deda1a35419accd193.1222258080.git.elliot.li.tech@gmail.com>
2008-09-24 12:24 ` Yan Li
2008-09-24 12:54   ` Laurent Vivier
2008-09-24 13:10     ` Yan Li
2008-09-24 14:16   ` Joerg Roedel
2008-09-25  2:51     ` Yan Li
2008-09-24 16:39   ` Yinghai Lu [this message]
2008-09-25  2:52     ` Yan Li
2008-09-25 14:18     ` Yan Li
2008-09-25 17:13       ` Yinghai Lu
2008-09-26  9:50         ` Yan Li
2008-10-01 20:03   ` Pavel Machek
2008-10-05 12:05     ` Yan Li

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=86802c440809240939h63b14efdm1382ffe4c44c6660@mail.gmail.com \
    --to=yinghai@kernel.org \
    --cc=elliot.li.tech@gmail.com \
    --cc=hpa@zytor.com \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nancydreaming@gmail.com \
    --cc=rjmaomao@gmail.com \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®