From: keith mannthey <kmannth@us.ibm.com>
To: lhms-devel <lhms-devel@lists.sourceforge.net>
Cc: linux-mm <linux-mm@kvack.org>, dave hansen <haveblue@us.ibm.com>,
kame <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [RFC] Patch [3/4] x86_64 sparsmem add - acpi added pages are not reserved?
Date: Fri, 23 Jun 2006 19:06:03 -0700 [thread overview]
Message-ID: <1151114763.7094.52.camel@keithlap> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
I got everything in place to do a working hot-add with 2.6.17-mm1 and I
ran into another trouble spot.
I added the memory just fine(new device is sysfs) but when I went to on-
line them in sysfs I tripped over the little section of code this patch
comments out. I was get device not ready messages on my console and the
comment printed in my kernel log.
With hacked acpi drivers outside of -mm I don't run into the problem
so I think something is a little off in -mm.
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>
[-- Attachment #2: patch-2.6.17-mm1-reservehack --]
[-- Type: text/x-patch, Size: 710 bytes --]
diff -urN linux-2.6.17-mm1-orig/drivers/base/memory.c linux-2.6.17-mm1/drivers/base/memory.c
--- linux-2.6.17-mm1-orig/drivers/base/memory.c 2006-06-23 16:12:01.000000000 -0400
+++ linux-2.6.17-mm1/drivers/base/memory.c 2006-06-23 20:04:04.000000000 -0400
@@ -163,9 +163,9 @@
/*
* The probe routines leave the pages reserved, just
* as the bootmem code does. Make sure they're still
- * that way.
+ * that way. UNLESS you do real hot add?
*/
- if (action == MEM_ONLINE) {
+/* if (action == MEM_ONLINE) {
for (i = 0; i < PAGES_PER_SECTION; i++) {
if (PageReserved(first_page+i))
continue;
@@ -176,6 +176,7 @@
return -EBUSY;
}
}
+*/
switch (action) {
case MEM_ONLINE:
next reply other threads:[~2006-06-24 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 2:06 keith mannthey [this message]
2006-06-24 7:38 ` 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=1151114763.7094.52.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.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