public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joerg Roedel" <joerg.roedel@amd.com>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] X86: don't print a warning when MTRR are blank and running in KVM
Date: Fri, 22 Feb 2008 12:18:04 +0100	[thread overview]
Message-ID: <20080222111804.GB6504@amd.com> (raw)
In-Reply-To: <86802c440802211154h28ef0170m59c42bdd8de76358@mail.gmail.com>

On Thu, Feb 21, 2008 at 11:54:00AM -0800, Yinghai Lu wrote:
> On Thu, Feb 21, 2008 at 6:50 AM, Joerg Roedel <joerg.roedel@amd.com> wrote:
> > Inside a KVM virtual machine the MTRRs are usually blank. This confuses Linux
> >  and causes a warning message at boot. This patch removes that warning message
> >  when running Linux as a KVM guest.
> >
> >  Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
> >  ---
> >   arch/x86/kernel/cpu/mtrr/main.c |    7 +++++--
> >   1 files changed, 5 insertions(+), 2 deletions(-)
> >
> >  diff --git a/arch/x86/kernel/cpu/mtrr/main.c b/arch/x86/kernel/cpu/mtrr/main.c
> >  index b6e136f..47e624c 100644
> >  --- a/arch/x86/kernel/cpu/mtrr/main.c
> >  +++ b/arch/x86/kernel/cpu/mtrr/main.c
> >  @@ -43,6 +43,7 @@
> >   #include <asm/uaccess.h>
> >   #include <asm/processor.h>
> >   #include <asm/msr.h>
> >  +#include <asm/kvm_para.h>
> >   #include "mtrr.h"
> >
> >   u32 num_var_ranges = 0;
> >  @@ -687,12 +688,14 @@ int __init mtrr_trim_uncached_memory(unsigned long end_pfn)
> >         }
> >
> >         /* kvm/qemu doesn't have mtrr set right, don't trim them all */
> >  -       if (!highest_pfn) {
> >  +       if (!highest_pfn && !kvm_para_available()) {
> >                 printk(KERN_WARNING "WARNING: strange, CPU MTRRs all blank?\n");
> >                 WARN_ON(1);
> >  -               return 0;
> >         }
> >
> >  +       if (!highest_pfn)
> >  +               return 0;
> >  +
> >         if (highest_pfn < end_pfn) {
> >                 printk(KERN_WARNING "WARNING: BIOS bug: CPU MTRRs don't cover"
> >                         " all of memory, losing %luMB of RAM.\n",
> >  --
> >  1.5.3.7
> >
> 
> Doest that WARN_ON(1) hurt?

Yes. It inidicates a problem where there isn't one. In a virtual machine
MTRRs make absolutly no sense and so they should all be blank there.

Joerg

-- 
           |           AMD Saxony Limited Liability Company & Co. KG
 Operating |         Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 System    |                  Register Court Dresden: HRA 4896
 Research  |              General Partner authorized to represent:
 Center    |             AMD Saxony LLC (Wilmington, Delaware, US)
           | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy



  reply	other threads:[~2008-02-22 11:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 14:50 [PATCH] X86: don't print a warning when MTRR are blank and running in KVM Joerg Roedel
2008-02-21 19:54 ` Yinghai Lu
2008-02-22 11:18   ` Joerg Roedel [this message]
2008-02-21 20:37 ` Ingo Molnar
2008-02-21 22:31   ` H. Peter Anvin
2008-02-22  9:45     ` Ingo Molnar
2008-02-22  9:58       ` H. Peter Anvin
2008-02-22 10:00         ` Ingo Molnar
2008-02-22 10:04           ` H. Peter Anvin
2008-02-22 11:15           ` Joerg Roedel
2008-02-22 12:48             ` Ingo Molnar

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=20080222111804.GB6504@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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