[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080930031922.22950.84239.stgit@jbrandeb-bw.jf.intel.com>
Date: Mon, 29 Sep 2008 20:19:22 -0700
From: Jesse Brandeburg <jesse.brandeburg@...el.com>
To: linux-kernel@...r.kernel.org
Cc: linux-netdev@...r.kernel.org, kkeil@...e.de, agospoda@...hat.com,
arjan@...ux.intel.com, david.graham@...el.com,
bruce.w.allan@...el.com, jkosina@...e.cz, john.ronciak@...el.com,
tglx@...utronix.de, chris.jones@...onical.com,
tim.gardner@...el.com, airlied@...il.com,
Bruce Allan <bruce.w.allan@...el.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Ingo Molnar <mingo@...e.hu>
Subject: [RFC PATCH 01/12] x86: export set_memory_ro and set_memory_rw
From: Bruce Allan <bruce.w.allan@...el.com>
Export set_memory_ro() and set_memory_rw() calls for use by drivers that need
to have more debug information about who might be writing to memory space.
this was initially developed for use while debugging a memory corruption
problem with e1000e.
Ingo Molnar <mingo@...e.hu> said:
>> +EXPORT_SYMBOL(set_memory_rw);
> that's fine, as long as you make it kernel-internal EXPORT_SYMBOL_GPL()
patch was modified with this suggestion.
Signed-off-by: Bruce Allan <bruce.w.allan@...el.com>
Signed-off-by: Jesse Brandeburg <jesse.brandeburg@...el.com>
Acked-by: Ingo Molnar <mingo@...e.hu>
---
arch/x86/mm/pageattr.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c
index 43e2f84..62c1eef 100644
--- a/arch/x86/mm/pageattr.c
+++ b/arch/x86/mm/pageattr.c
@@ -906,11 +906,13 @@ int set_memory_ro(unsigned long addr, int numpages)
{
return change_page_attr_clear(addr, numpages, __pgprot(_PAGE_RW));
}
+EXPORT_SYMBOL_GPL(set_memory_ro);
int set_memory_rw(unsigned long addr, int numpages)
{
return change_page_attr_set(addr, numpages, __pgprot(_PAGE_RW));
}
+EXPORT_SYMBOL_GPL(set_memory_rw);
int set_memory_np(unsigned long addr, int numpages)
{
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists