From: "Jan Beulich" <JBeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] x86: allow SRAT to be used on 32-bit systems with memory beyond 4G
Date: Wed, 24 Feb 2010 13:44:15 +0000 [thread overview]
Message-ID: <4B853B3F0200007800031005@vpn.id2.novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
Signed-off-by: Jan Beulich <jbeulich@novell.com>
--- 2010-02-19.orig/xen/arch/x86/srat.c 2010-01-13 18:58:11.000000000 +0100
+++ 2010-02-19/xen/arch/x86/srat.c 2010-02-24 14:25:50.000000000 +0100
@@ -59,7 +59,7 @@ __devinit int setup_node(int pxm)
return pxm2node[pxm];
}
-int valid_numa_range(unsigned long start, unsigned long end, int node)
+int valid_numa_range(u64 start, u64 end, int node)
{
int i;
@@ -74,7 +74,7 @@ int valid_numa_range(unsigned long start
return 0;
}
-static __init int conflicting_memblks(unsigned long start, unsigned long end)
+static __init int conflicting_memblks(u64 start, u64 end)
{
int i;
--- 2010-02-19.orig/xen/include/asm-x86/numa.h 2010-01-13 18:58:11.000000000 +0100
+++ 2010-02-19/xen/include/asm-x86/numa.h 2010-02-24 14:26:56.000000000 +0100
@@ -76,11 +76,11 @@ static inline __attribute__((pure)) int
#define node_end_pfn(nid) (NODE_DATA(nid)->node_start_pfn + \
NODE_DATA(nid)->node_spanned_pages)
-extern int valid_numa_range(unsigned long start, unsigned long end, int node);
+extern int valid_numa_range(u64 start, u64 end, int node);
#else
#define init_cpu_to_node() do {} while (0)
#define clear_node_cpumask(cpu) do {} while (0)
-#define valid_numa_range(start, end, node) {return 1;}
+#define valid_numa_range(start, end, node) 1
#endif
void srat_parse_regions(u64 addr);
[-- Attachment #2: xen-srat-32bit.patch --]
[-- Type: text/plain, Size: 1405 bytes --]
Signed-off-by: Jan Beulich <jbeulich@novell.com>
--- 2010-02-19.orig/xen/arch/x86/srat.c 2010-01-13 18:58:11.000000000 +0100
+++ 2010-02-19/xen/arch/x86/srat.c 2010-02-24 14:25:50.000000000 +0100
@@ -59,7 +59,7 @@ __devinit int setup_node(int pxm)
return pxm2node[pxm];
}
-int valid_numa_range(unsigned long start, unsigned long end, int node)
+int valid_numa_range(u64 start, u64 end, int node)
{
int i;
@@ -74,7 +74,7 @@ int valid_numa_range(unsigned long start
return 0;
}
-static __init int conflicting_memblks(unsigned long start, unsigned long end)
+static __init int conflicting_memblks(u64 start, u64 end)
{
int i;
--- 2010-02-19.orig/xen/include/asm-x86/numa.h 2010-01-13 18:58:11.000000000 +0100
+++ 2010-02-19/xen/include/asm-x86/numa.h 2010-02-24 14:26:56.000000000 +0100
@@ -76,11 +76,11 @@ static inline __attribute__((pure)) int
#define node_end_pfn(nid) (NODE_DATA(nid)->node_start_pfn + \
NODE_DATA(nid)->node_spanned_pages)
-extern int valid_numa_range(unsigned long start, unsigned long end, int node);
+extern int valid_numa_range(u64 start, u64 end, int node);
#else
#define init_cpu_to_node() do {} while (0)
#define clear_node_cpumask(cpu) do {} while (0)
-#define valid_numa_range(start, end, node) {return 1;}
+#define valid_numa_range(start, end, node) 1
#endif
void srat_parse_regions(u64 addr);
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2010-02-24 13:44 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=4B853B3F0200007800031005@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.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).