linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Greg Thelen <gthelen@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	cl@linux-foundation.com
Subject: Re: mmotm boot panic bootmem-avoid-dma32-zone-by-default.patch
Date: Thu, 11 Mar 2010 11:54:00 +0100	[thread overview]
Message-ID: <4B98CBC8.6080008@gmail.com> (raw)
In-Reply-To: <4B92FE9E.90600@kernel.org>

On 03/07/2010 02:17 AM, Yinghai Lu wrote:
> On 03/05/2010 02:26 AM, Jiri Slaby wrote:
>> On 03/05/2010 10:04 AM, Yinghai Lu wrote:
>>> according to context
>>> http://patchwork.kernel.org/patch/73893/
>>>
>>> Jiri,
>>> please check current linus tree still have problem about mem_map is using that much low mem?
>>
>> Hi!
>>
>> Sorry, I don't have direct access to the machine. I might try to ask the
>> owners to do so.
>>
>>> on my 1024g system first node has 128G ram, [2g, 4g) are mmio range.
>>
>> So where gets your mem_map allocated (I suppose you're running flat model)?
>
> what kernel version? 2.6.27?

Hi, yes, it is 2.6.27.

> x86 64bit now only support SPARSEMEM.


-- 
js

  reply	other threads:[~2010-03-11 10:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49b004811003041321g2567bac8yb73235be32a27e7c@mail.gmail.com>
     [not found] ` <20100305032106.GA12065@cmpxchg.org>
2010-03-05  9:04   ` mmotm boot panic bootmem-avoid-dma32-zone-by-default.patch Yinghai Lu
2010-03-05 10:26     ` Jiri Slaby
2010-03-05 20:27       ` Yinghai Lu
2010-03-07  1:17       ` Yinghai Lu
2010-03-11 10:54         ` Jiri Slaby [this message]
2010-03-11 20:12           ` Yinghai Lu
2010-03-11 21:40             ` Jiri Slaby
2010-03-11 21:42               ` Yinghai Lu
2010-03-05 13:08     ` Johannes Weiner
     [not found]   ` <49b004811003042117n720f356h7e10997a1a783475@mail.gmail.com>
2010-03-05 18:41     ` Yinghai Lu
2010-03-05 19:09       ` Greg Thelen
2010-03-05 20:38       ` [PATCH] x86/bootmem: introduce bootmem_default_goal Yinghai Lu
2010-03-06  5:44         ` please don't apply : bootmem: avoid DMA32 zone by default Yinghai Lu
2010-03-07  0:22           ` Andrew Morton
2010-03-07  0:42             ` Yinghai Lu
2010-03-07  0:53               ` Yinghai Lu
2010-03-07  2:15                 ` [PATCH] sparsemem: on no vmemmap path put mem_map on node high too Yinghai Lu
2010-03-07  1:03             ` please don't apply : bootmem: avoid DMA32 zone by default Paul Mackerras
2010-03-07  1:48               ` Stephen Rothwell
2010-03-07  9:16               ` Russell King
2010-03-05 23:58       ` mmotm boot panic bootmem-avoid-dma32-zone-by-default.patch Johannes Weiner
2010-03-06  1:50         ` Yinghai Lu
2010-03-06  2:24           ` Johannes Weiner
2010-03-06  2:31             ` Yinghai Lu

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=4B98CBC8.6080008@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.com \
    --cc=gthelen@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yinghai@kernel.org \
    /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).