LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [patch] x86: Kill bogus MTRR warning when running under vmware
Date: Mon, 3 Nov 2008 09:48:42 +0100	[thread overview]
Message-ID: <20081103084842.GD11730@elte.hu> (raw)
In-Reply-To: <20081031170355.5368be60@redhat.com>


* Chuck Ebbert <cebbert@redhat.com> wrote:

> x86: Kill bogus MTRR warning when running under vmware
> 
> The warning is suppressed when running under KVM, but VMware
> guests also have empty MTRRs.
> 
> Fixes:
> https://bugzilla.redhat.com/show_bug.cgi?id=468845

we are working on proper "are we within vmware" detection support. 
Patches already exist and it is useful to know it for other reasons as 
wel.

	Ingo

      reply	other threads:[~2008-11-03  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 21:03 [patch] x86: Kill bogus MTRR warning when running under vmware Chuck Ebbert
2008-11-03  8:48 ` Ingo Molnar [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=20081103084842.GD11730@elte.hu \
    --to=mingo@elte.hu \
    --cc=cebbert@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).