From: Jiri Slaby <jirislaby@gmail.com>
To: akpm@linux-foundation.org
Cc: Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin\"" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [PATCH 1/1] define node_*_pfn for non-NUMA builds
Date: Fri, 21 Aug 2009 09:46:46 +0200 [thread overview]
Message-ID: <1250840806-14232-1-git-send-email-jirislaby@gmail.com> (raw)
FWIW "Latest fs/proc/kcore updates" in the changelog are these
from mmotm:
> kcore-use-registerd-physmem-information.patch
> kcore-use-registerd-physmem-information-fix.patch
> kcore-use-registerd-physmem-information-checkpatch-fixes.patch
--
Latest fs/proc/kcore updates need node_end_pfn. To avoid a compiler
error:
fs/proc/kcore.c: In function ‘kcore_update_ram’:
fs/proc/kcore.c:200: error: implicit declaration of function ‘node_end_pfn’
define node_start_pfn and node_end_pfn as simple contig_page_data
accessors on !NUMA builds.
Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
---
include/linux/mmzone.h | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 9c50309..6789900 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -771,6 +771,9 @@ extern char numa_zonelist_order[];
extern struct pglist_data contig_page_data;
#define NODE_DATA(nid) (&contig_page_data)
#define NODE_MEM_MAP(nid) mem_map
+#define node_start_pfn(nid) (contig_page_data.node_start_pfn)
+#define node_end_pfn(nid) (contig_page_data.node_start_pfn + \
+ contig_page_data.node_spanned_pages)
#else /* CONFIG_NEED_MULTIPLE_NODES */
--
1.6.3.3
reply other threads:[~2009-08-21 7:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1250840806-14232-1-git-send-email-jirislaby@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@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
all inboxes | Powered by JetHome®