All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
	j_kernel@hoblitt.com
Subject: Re: [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable
Date: Fri, 22 Aug 2008 05:51:44 +0200	[thread overview]
Message-ID: <20080822035144.GC30284@elte.hu> (raw)
In-Reply-To: <86802c440808210839u452d9440kd7d12694db515411@mail.gmail.com>


* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

> On Thu, Aug 21, 2008 at 4:56 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Ingo Molnar <mingo@elte.hu> wrote:
> >
> >>
> >> * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> >>
> >> > [PATCH] x86_64: printout msr
> >>
> >> looks rather useful - added it to tip/x86/debug.
> >
> > fails to build with the attached config:
> >
> > arch/x86/kernel/cpu/common_64.c: In function 'print_cpu_msr':
> > arch/x86/kernel/cpu/common_64.c:456: error: implicit declaration of function 'rdmsrl_amd_safe'
> > arch/x86/kernel/cpu/common_64.c: In function 'print_cpu_info':
> > arch/x86/kernel/cpu/common_64.c:486: error: 'struct cpuinfo_x86' has no member named 'cpu_index'
> >
> > i realize that this wasnt sent for inclusion, but i think it would make
> > sense to tidy it up and integrate it.
> 
> that was one tool to verify if BIOS does right thing about some special bits.
> 
> it seems it doesn't compile when xen etc is enable in config.

yeah - but would be nice to fix it, as it's a useful diagnostic patch. 
If people have similar problems in the future they can boot their distro 
kernels with show_mtrr=x to get a MTRR dump.

	Ingo

  reply	other threads:[~2008-08-22  3:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11388-27@http.bugzilla.kernel.org/>
2008-08-21  1:04 ` [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable Andrew Morton
2008-08-21  1:20   ` Yinghai Lu
2008-08-21  1:49     ` Yinghai Lu
2008-08-21 11:44       ` Ingo Molnar
2008-08-21 11:56         ` Ingo Molnar
2008-08-21 15:39           ` Yinghai Lu
2008-08-22  3:51             ` Ingo Molnar [this message]
2008-08-22  4:45               ` Yinghai Lu
2008-08-21 20:55       ` Joshua Hoblitt
2008-08-21 21:51         ` Yinghai Lu
2008-08-21 23:33           ` Joshua Hoblitt
2008-08-22  0:10             ` Joshua Hoblitt
2008-08-22  0:28               ` Yinghai Lu
2008-08-22  0:29                 ` Joshua Hoblitt
2008-08-22  1:00                   ` Joshua Hoblitt
2008-08-22  1:10                     ` Joshua Hoblitt
2008-08-22  1:55                       ` Yinghai Lu
2008-08-22  2:15                         ` Joshua Hoblitt
2008-08-22  2:26                           ` Yinghai Lu
2008-08-22  3:24                             ` Yinghai Lu
2008-08-22  3:50                               ` Ingo Molnar
2008-08-22  3:56                                 ` Ingo Molnar
2008-08-22  4:48                                   ` Yinghai Lu
2008-08-23  0:22                                     ` Joshua Hoblitt
2008-08-23  5:52                                       ` Yinghai Lu
2008-08-23 10:43                                         ` Ingo Molnar
2008-08-26  8:35                                           ` Joshua Hoblitt
2008-08-26  8:42                                             ` Ingo Molnar
2008-08-25 21:43                                   ` Joshua Hoblitt
2008-08-22  6:16                                 ` Yinghai Lu
2008-08-22  6:24                                   ` Ingo Molnar
2008-08-23 23:53                                     ` Arjan van de Ven
2008-08-25  9:17                                       ` Ingo Molnar
2008-08-22  3:26                             ` Joshua Hoblitt

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=20080822035144.GC30284@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=j_kernel@hoblitt.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 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.