From: Oleg Nesterov <oleg@tv-sign.ru>
To: linux-kernel@vger.kernel.org
Cc: Matt Mackall <mpm@selenic.com>
Subject: [RFC] __initdata strings
Date: Sun, 10 Oct 2004 19:28:29 +0400 [thread overview]
Message-ID: <4169551D.A884778D@tv-sign.ru> (raw)
Hello.
This patch is not intended for inclusion, just for illustration.
__init functions leaves strings (mainly printk's arguments) in
.data section. It make sense to move them in .init.data.
Is there anyone else who would consider this useful?
Oleg.
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
diff -rup 2.6.9-rc3-clean/include/linux/init.h 2.6.9-rc3-i_str/include/linux/init.h
--- 2.6.9-rc3-clean/include/linux/init.h Sun Oct 10 11:48:46 2004
+++ 2.6.9-rc3-i_str/include/linux/init.h Sun Oct 10 11:55:07 2004
@@ -61,6 +61,31 @@
/*
* Used for initialization calls..
*/
+
+#define I_STRING(str) \
+({ \
+ static char data[] __initdata = (str); \
+ data; \
+})
+
+#if defined(__GNUC__) && (__GNUC__ >= 3)
+#define CK_FMTSTR(expr) do if (0) { expr; } while (0)
+#else
+#define CK_FMTSTR(expr) do ; while (0)
+#endif
+
+#define i_printk(fmt, args...) \
+({ \
+ CK_FMTSTR(printk(fmt , ##args)); \
+ printk(I_STRING(fmt) , ##args); \
+})
+
+#define i_panic(fmt, args...) \
+({ \
+ CK_FMTSTR(panic(fmt , ##args)); \
+ panic(I_STRING(fmt) , ##args); \
+})
+
typedef int (*initcall_t)(void);
typedef void (*exitcall_t)(void);
diff -rup 2.6.9-rc3-clean/init/do_mounts.c 2.6.9-rc3-i_str/init/do_mounts.c
--- 2.6.9-rc3-clean/init/do_mounts.c Sun Oct 10 11:48:57 2004
+++ 2.6.9-rc3-i_str/init/do_mounts.c Sat Oct 9 18:18:30 2004
@@ -265,10 +265,10 @@ static int __init do_mount_root(char *na
sys_chdir("/root");
ROOT_DEV = current->fs->pwdmnt->mnt_sb->s_dev;
- printk("VFS: Mounted root (%s filesystem)%s.\n",
+ i_printk("VFS: Mounted root (%s filesystem)%s.\n",
current->fs->pwdmnt->mnt_sb->s_type->name,
current->fs->pwdmnt->mnt_sb->s_flags & MS_RDONLY ?
- " readonly" : "");
+ I_STRING(" readonly") : "");
return 0;
}
@@ -296,13 +296,13 @@ retry:
* and bad superblock on root device.
*/
__bdevname(ROOT_DEV, b);
- printk("VFS: Cannot open root device \"%s\" or %s\n",
+ i_printk("VFS: Cannot open root device \"%s\" or %s\n",
root_device_name, b);
- printk("Please append a correct \"root=\" boot option\n");
+ i_printk("Please append a correct \"root=\" boot option\n");
- panic("VFS: Unable to mount root fs on %s", b);
+ i_panic("VFS: Unable to mount root fs on %s", b);
}
- panic("VFS: Unable to mount root fs on %s", __bdevname(ROOT_DEV, b));
+ i_panic("VFS: Unable to mount root fs on %s", __bdevname(ROOT_DEV, b));
out:
putname(fs_names);
}
@@ -336,7 +336,7 @@ void __init change_floppy(char *fmt, ...
sys_ioctl(fd, FDEJECT, 0);
sys_close(fd);
}
- printk(KERN_NOTICE "VFS: Insert %s and press ENTER\n", buf);
+ i_printk(KERN_NOTICE "VFS: Insert %s and press ENTER\n", buf);
fd = sys_open("/dev/console", O_RDWR, 0);
if (fd >= 0) {
sys_ioctl(fd, TCGETS, (long)&termios);
@@ -357,7 +357,7 @@ void __init mount_root(void)
if (mount_nfs_root())
return;
- printk(KERN_ERR "VFS: Unable to mount root fs via NFS, trying floppy.\n");
+ i_printk(KERN_ERR "VFS: Unable to mount root fs via NFS, trying floppy.\n");
ROOT_DEV = Root_FD0;
}
#endif
next reply other threads:[~2004-10-10 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 15:28 Oleg Nesterov [this message]
2004-10-10 16:31 ` Matt Mackall
2004-10-10 16:40 ` Arnaldo Carvalho de Melo
[not found] <2NNXM-1fZ-5@gated-at.bofh.it>
2004-10-10 15:45 ` Andi Kleen
2004-10-10 16:12 ` Oleg Nesterov
2004-10-10 16:36 ` Arnaldo Carvalho de Melo
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=4169551D.A884778D@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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
all inboxes | Powered by JetHome®