From: Marco Stornelli <marco.stornelli@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Tim Bird <tim.bird@am.sony.com>, andi@firstfloor.org
Subject: [PATCH] archs: add ioremap_change_write_prot
Date: Sun, 24 Oct 2010 10:41:31 +0200 [thread overview]
Message-ID: <4CC3F13B.4030107@gmail.com> (raw)
From: Marco Stornelli <marco.stornelli@gmail.com>
This patch adds a new function called ioremap_change_write_prot.
Goal of this patch is to create a general function for all archs to be
able to change a write protection of a memory mapped area. x86
has already got a similar framework, so this function is only
a wrapper. Next target will be arm and powerpc. This function
will be used by Pramfs (see its latest review).
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
---
diff -Nurp linux-2.6.36-orig/arch/x86/mm/ioremap.c linux-2.6.36/arch/x86/mm/ioremap.c
--- linux-2.6.36-orig/arch/x86/mm/ioremap.c 2010-09-13 01:07:37.000000000 +0200
+++ linux-2.6.36/arch/x86/mm/ioremap.c 2010-10-24 10:03:36.000000000 +0200
@@ -50,6 +50,27 @@ int ioremap_change_attr(unsigned long va
return err;
}
+int ioremap_change_write_prot(unsigned long vaddr, unsigned long size,
+ unsigned int rw)
+{
+ unsigned long nrpages = size >> PAGE_SHIFT;
+ int ret;
+
+ /* Page aligned */
+ vaddr &= PAGE_MASK;
+
+ if (size & (PAGE_SIZE - 1))
+ nrpages++;
+
+ if (rw)
+ ret = set_memory_rw(vaddr, nrpages);
+ else
+ ret = set_memory_ro(vaddr, nrpages);
+
+ return ret;
+}
+EXPORT_SYMBOL(ioremap_change_write_prot);
+
/*
* Remap an arbitrary physical address space into the kernel virtual
* address space. Needed when the kernel wants to access high addresses
--- linux-2.6.36-orig/arch/Kconfig 2010-09-13 01:07:37.000000000 +0200
+++ linux-2.6.36/arch/Kconfig 2010-10-23 09:29:56.000000000 +0200
@@ -83,6 +83,9 @@ config USER_RETURN_NOTIFIER
config HAVE_IOREMAP_PROT
bool
+config HAVE_IOREMAP_CHANGE_WRITE_PROT
+ bool
+
config HAVE_KPROBES
bool
--- linux-2.6.36-orig/arch/x86/Kconfig 2010-09-13 01:07:37.000000000 +0200
+++ linux-2.6.36/arch/x86/Kconfig 2010-10-23 09:09:06.000000000 +0200
@@ -26,6 +26,7 @@ config X86
select HAVE_OPROFILE
select HAVE_PERF_EVENTS if (!M386 && !M486)
select HAVE_IOREMAP_PROT
+ select HAVE_IOREMAP_CHANGE_WRITE_PROT
select HAVE_KPROBES
select ARCH_WANT_OPTIONAL_GPIOLIB
select ARCH_WANT_FRAME_POINTERS
diff -Nurp linux-2.6.36-orig/arch/x86/include/asm/io.h linux-2.6.36/arch/x86/include/asm/io.h
--- linux-2.6.36-orig/arch/x86/include/asm/io.h 2010-09-13 01:07:37.000000000 +0200
+++ linux-2.6.36/arch/x86/include/asm/io.h 2010-10-23 09:11:37.000000000 +0200
@@ -333,6 +333,8 @@ extern void unxlate_dev_mem_ptr(unsigned
extern int ioremap_change_attr(unsigned long vaddr, unsigned long size,
unsigned long prot_val);
+extern int ioremap_change_write_prot(unsigned long vaddr, unsigned long size,
+ unsigned int rw);
extern void __iomem *ioremap_wc(resource_size_t offset, unsigned long size);
/*
next reply other threads:[~2010-10-24 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 8:41 Marco Stornelli [this message]
2010-10-26 10:56 ` [PATCH] archs: add ioremap_change_write_prot Marco Stornelli
2010-10-26 13:14 ` Andi Kleen
2010-10-26 16:24 ` Thomas Gleixner
2010-10-27 6:55 ` Marco Stornelli
2010-10-27 7:59 ` Andi Kleen
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=4CC3F13B.4030107@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.