linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: kmannth@us.ibm.com
Cc: lhms-devel@lists.sourceforge.net, linux-mm@kvack.org,
	haveblue@us.ibm.com
Subject: Re: [RFC] Patch [3/4] x86_64 sparsmem add - acpi added pages are not reserved?
Date: Sat, 24 Jun 2006 16:38:14 +0900	[thread overview]
Message-ID: <20060624163814.a9032a49.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1151114763.7094.52.camel@keithlap>

On Fri, 23 Jun 2006 19:06:03 -0700
keith mannthey <kmannth@us.ibm.com> wrote:

>   The code is expecting the added but not on-lined code to be marked
> reserved. This isn't happening for my ACPI hot-add on x86_64. I am not
> sure who in this call path needs to reserve the pages or if the check
> for reserve is a valid with this new hot-add code.    
> 
> Any ideas?
> 
> Signed-off-by:  Keith Mannthey <kmannth@us.ibm.com>
> 
/*	if (action == MEM_ONLINE) {
 		for (i = 0; i < PAGES_PER_SECTION; i++) {
 			if (PageReserved(first_page+i))
 				continue;
@@ -176,6 +176,7 @@
 			return -EBUSY;
 		}
 	}
+*/
Pages are marked as Reserved before onlined. Then, all pages in the area
should be reserved.(and sparsemem allocates SECTION_SIZE aligned memmap.)
(see __add_zone() -> memmap_init_zone().)
newly initialized memmap are marked as reserved. 
Plz confirm your "currently unused memmap" is properly marked as reserved.

It's important to find "why" before doing this kind of workaround.

Hmm... at first, could you show your /proc/iomem before and after
hot-add event ?

Thanks,
-Kame

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2006-06-24  7:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24  2:06 keith mannthey
2006-06-24  7:38 ` KAMEZAWA Hiroyuki [this message]

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=20060624163814.a9032a49.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=haveblue@us.ibm.com \
    --cc=kmannth@us.ibm.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-mm@kvack.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