From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make modules work in Linus' tree on ARM
Date: Wed, 17 Sep 2003 10:23:25 +0100 [thread overview]
Message-ID: <20030917102325.A11125@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030814173249.C332@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, Aug 14, 2003 at 05:32:49PM +0100
On Thu, Aug 14, 2003 at 05:32:49PM +0100, Russell King wrote:
> I was thinking afterwards about a patch to allow /proc/kcore to be
> entirely disabled and dropped out of the kernel - we already select
> between a.out and ELF.
Ok, it's been a while, but here's the patch which does this - it only
drops /proc/kcore out of the kernel for ARM.
diff -u orig/fs/Kconfig linux/fs/Kconfig
--- orig/fs/Kconfig Tue Sep 9 23:08:10 2003
+++ linux/fs/Kconfig Sat Aug 23 10:12:27 2003
@@ -761,6 +761,10 @@
This option will enlarge your kernel by about 67 KB. Several
programs depend on this, so everyone should say Y here.
+config PROC_KCORE
+ bool
+ default y if !ARM
+
config DEVFS_FS
bool "/dev file system support (EXPERIMENTAL)"
depends on EXPERIMENTAL
diff -u orig/fs/proc/Makefile linux/fs/proc/Makefile
--- orig/fs/proc/Makefile Thu Sep 4 23:58:31 2003
+++ linux/fs/proc/Makefile Thu Aug 14 18:27:31 2003
@@ -8,6 +8,7 @@
proc-$(CONFIG_MMU) := task_mmu.o
proc-y += inode.o root.o base.o generic.o array.o \
- kmsg.o proc_tty.o proc_misc.o kcore.o
+ kmsg.o proc_tty.o proc_misc.o
-proc-$(CONFIG_PROC_DEVICETREE) += proc_devtree.o
+proc-$(CONFIG_PROC_KCORE) += kcore.o
+proc-$(CONFIG_PROC_DEVICETREE) += proc_devtree.o
diff -u orig/fs/proc/proc_misc.c linux/fs/proc/proc_misc.c
--- orig/fs/proc/proc_misc.c Tue Sep 9 23:08:11 2003
+++ linux/fs/proc/proc_misc.c Mon Sep 8 22:52:18 2003
@@ -685,12 +685,14 @@
#ifdef CONFIG_MODULES
create_seq_entry("modules", 0, &proc_modules_operations);
#endif
+#ifdef CONFIG_PROC_KCORE
proc_root_kcore = create_proc_entry("kcore", S_IRUSR, NULL);
if (proc_root_kcore) {
proc_root_kcore->proc_fops = &proc_kcore_operations;
proc_root_kcore->size =
(size_t)high_memory - PAGE_OFFSET + PAGE_SIZE;
}
+#endif
if (prof_on) {
entry = create_proc_entry("profile", S_IWUSR | S_IRUGO, NULL);
if (entry) {
--
Russell King (rmk@arm.linux.org.uk) http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
2.6 ARM Linux - http://www.arm.linux.org.uk/
2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2003-09-17 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 12:08 [PATCH] Make modules work in Linus' tree on ARM Russell King
2003-08-14 16:19 ` Linus Torvalds
2003-08-14 16:32 ` Russell King
2003-09-17 9:23 ` Russell King [this message]
2003-08-14 16:47 ` Alan Cox
2003-08-14 16:55 ` John Levon
2003-08-14 17:06 ` Alan Cox
2003-08-14 17:19 ` Linus Torvalds
2003-08-14 17:14 ` Linus Torvalds
2003-08-14 17:30 ` John Levon
2003-08-14 19:18 ` [PATCH] Export pointer size in oprofilefs John Levon
2003-08-14 17:24 ` [PATCH] Make modules work in Linus' tree on ARM Russell King
2003-08-14 20:12 ` Eli Carter
2003-08-14 20:42 ` Russell King
2003-08-18 19:27 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-08-14 17:16 John Bradford
2003-08-14 17:42 Luck, Tony
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=20030917102325.A11125@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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