linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Yinghai Lu <yhlu.kernel.send@gmail.com>,
	linuxppc-dev@ozlabs.org, Badari Pulavarty <pbadari@us.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH] mm: make mem_map allocation continuous v2.
Date: Thu, 03 Apr 2008 16:19:09 +0530	[thread overview]
Message-ID: <47F4B625.7030007@linux.vnet.ibm.com> (raw)
In-Reply-To: <86802c440804022116j2a8fb745pf734f61542a8e287@mail.gmail.com>

Yinghai Lu wrote:
> On Wed, Apr 2, 2008 at 7:22 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>> On Wed, 2 Apr 2008 18:30:24 -0700 Yinghai Lu <yhlu.kernel.send@gmail.com> wrote:
>>
>>  > v2 replace:
>>  >       [PATCH] mm: make mem_map allocation continuous.
>>  >       [PATCH] mm: allocate section_map for sparse_init
>>  >       [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init
>>  >
>>
>>  err, no.
>>
>>
>>  >
>>  > diff --git a/mm/sparse.c b/mm/sparse.c
>>  > index f6a43c0..2881222 100644
>>  > --- a/mm/sparse.c
>>  > +++ b/mm/sparse.c
>>
>>  Sorry, but I'd rather not do it this way.  We presently have this:
>>
> 
> it replaces
> 
>>  mm-make-mem_map-allocation-continuous.patch
>>  mm-make-mem_map-allocation-continuous-checkpatch-fixes.patch
>>  mm-allocate-section_map-for-sparse_init.patch
>>  mm-allocate-section_map-for-sparse_init-update.patch
>>  mm-allocate-section_map-for-sparse_init-update-fix.patch
>>  mm-allocate-section_map-for-sparse_init-powerpc-fix.patch
> 
> others still needed
> 
> so mm-make-mem-map-allocation-continuous.patch will not break powerpc and ia64
> 
> YH
Hi,

Thanks, the patch fixes the issue. I am able to bootup without the kernel panic.

Tested-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> 

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

  reply	other threads:[~2008-04-03 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 22:25 [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init Yinghai Lu
2008-04-02 22:52 ` Andrew Morton
2008-04-03  0:44   ` Yinghai Lu
2008-04-03  1:30     ` [PATCH] mm: make mem_map allocation continuous v2 Yinghai Lu
2008-04-03  2:22       ` Andrew Morton
2008-04-03  4:16         ` Yinghai Lu
2008-04-03 10:49           ` Kamalesh Babulal [this message]
2008-04-03  3:22       ` Yasunori Goto
2008-04-03  1:43     ` [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init Yinghai Lu
2008-04-02 23:51 ` Badari Pulavarty
2008-04-03  0:47   ` 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=47F4B625.7030007@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@elte.hu \
    --cc=pbadari@us.ibm.com \
    --cc=yhlu.kernel.send@gmail.com \
    --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).