public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	lhms <lhms-devel@lists.sourceforge.net>
Subject: Re: [Lhms-devel] Re: 2.6.14-mm2
Date: Thu, 17 Nov 2005 09:10:03 +0900	[thread overview]
Message-ID: <437BCA5B.4080800@jp.fujitsu.com> (raw)
In-Reply-To: <1132158704.19290.3.camel@localhost>

Dave Hansen wrote:
> Hmmm.  I _think_ you're just trying to do some things at runtime that I
> didn't intend.  In the patch I pointed to in the last mail, look at what
> I did in hot_add_zone_init().  It does some of what
> free_area_init_core() does, but only the most minimal bits.  Basically:
> 
>        zone_wait_table_init(zone, size_pages);
>        init_currently_empty_zone(zone, phys_start_pfn, size_pages);
>        zone_pcp_init(zone);
> 
> Your way may also be valid, but I broke out init_currently_empty_zone()
> for a reason, and I think this was it.  I don't think we want to be
> calling free_area_init_core() itself at runtime.
> 

I understand what is missing..
"add new zone" function is not in -mm kernel.
So, I can't add new pages into Highmem which is empty at boot time.
Could you post your "add new zone" patch to -mm ?

-- Kame


  parent reply	other threads:[~2005-11-17  0:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11  4:35 2.6.14-mm2 Andrew Morton
2005-11-11  5:23 ` 2.6.14-mm2: loop detected in depmod Brice Goglin
2005-11-11  7:52   ` Antonino A. Daplas
2005-11-12  3:41     ` Brice Goglin
2005-11-11  5:49 ` 2.6.14-mm2 Reuben Farrelly
2005-11-11  6:07   ` 2.6.14-mm2 Andrew Morton
2005-11-11  8:28     ` 2.6.14-mm2 Reuben Farrelly
2005-11-11  8:55       ` 2.6.14-mm2 Andrew Morton
2005-11-11 13:28         ` 2.6.14-mm2 Reuben Farrelly
2005-11-11  8:54 ` 2.6.14-mm2 J.A. Magallon
2005-11-11 12:33 ` 2.6.14-mm2 Felipe Alfaro Solana
2005-11-11 16:40 ` [-mm patch] fs/ocfs2/file.c: make ocfs2_extend_allocation() static Adrian Bunk
2005-11-11 17:09 ` [-mm PATCH] slob: add kmem_set_shrinker Yoichi Yuasa
2005-11-11 19:14 ` 2.6.14-mm2 Badari Pulavarty
2005-11-11 19:21   ` 2.6.14-mm2 Andrew Morton
2005-11-11 19:32     ` 2.6.14-mm2 Badari Pulavarty
2005-11-11 22:32 ` 2.6.14-mm2 Michal Piotrowski
2005-11-11 22:37   ` 2.6.14-mm2 Michal Piotrowski
2005-11-11 23:01   ` 2.6.14-mm2 Andrew Morton
2005-11-11 23:28     ` [PATCH] nvidiafb: Fix bug in nvidiafb_pan_display Antonino A. Daplas
2005-11-11 23:38       ` Benjamin Herrenschmidt
2005-11-11 23:55         ` Antonino A. Daplas
2005-11-11 23:54       ` Michal Piotrowski
2005-11-11 23:30     ` 2.6.14-mm2 Michal Piotrowski
2005-11-12  0:45       ` 2.6.14-mm2 Antonino A. Daplas
2005-11-16  9:04 ` 2.6.14-mm2 KAMEZAWA Hiroyuki
2005-11-16 12:56 ` 2.6.14-mm2 KAMEZAWA Hiroyuki
2005-11-16 13:17   ` [Lhms-devel] 2.6.14-mm2 Dave Hansen
2005-11-16 16:02     ` Kamezawa Hiroyuki
2005-11-16 16:31       ` Dave Hansen
2005-11-16 16:39         ` Kamezawa Hiroyuki
2005-11-17  0:10         ` KAMEZAWA Hiroyuki [this message]
2005-11-17  9:16         ` KAMEZAWA Hiroyuki

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=437BCA5B.4080800@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.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