From: Brian Gerst <bgerst@didntduck.org>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Use .incbin for config_data.gz
Date: Sun, 25 Sep 2005 09:16:34 -0400 [thread overview]
Message-ID: <4336A332.9010906@didntduck.org> (raw)
In-Reply-To: <200509251213.56437.ioe-lkml@rameria.de>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
Ingo Oeser wrote:
> Hi Brian,
>
> On Saturday 24 September 2005 20:30, Brian Gerst wrote:
>
>>Instead of creating config_data.h, use .incbin in inline assembly to
>>directly include config_data.gz.
>
>
> Good idea, but please make this .rodata instead of .data,
> since this isn't going to be modified.
>
> Regards
>
> Ingo Oeser
>
New patch putting the config data in .rodata.
[-- Attachment #2: 0002-Use-.incbin-for-config_data.gz.txt --]
[-- Type: text/plain, Size: 2229 bytes --]
Subject: [PATCH] Use .incbin for config_data.gz
Instead of creating config_data.h, use .incbin in inline assembly to
directly include config_data.gz.
Signed-off-by: Brian Gerst <bgerst@didntduck.org>
---
kernel/Makefile | 9 +--------
kernel/configs.c | 18 +++++++++++++-----
2 files changed, 14 insertions(+), 13 deletions(-)
5674a0222370187dbe3401cb7a380c491a13f167
diff --git a/kernel/Makefile b/kernel/Makefile
--- a/kernel/Makefile
+++ b/kernel/Makefile
@@ -41,16 +41,9 @@ ifneq ($(CONFIG_SCHED_NO_NO_OMIT_FRAME_P
CFLAGS_sched.o := $(PROFILING) -fno-omit-frame-pointer
endif
-$(obj)/configs.o: $(obj)/config_data.h
+$(obj)/configs.o: $(obj)/config_data.gz
-# config_data.h contains the same information as ikconfig.h but gzipped.
# Info from config_data can be extracted from /proc/config*
targets += config_data.gz
$(obj)/config_data.gz: .config FORCE
$(call if_changed,gzip)
-
-quiet_cmd_ikconfiggz = IKCFG $@
- cmd_ikconfiggz = (echo "static const char kernel_config_data[] = MAGIC_START"; cat $< | scripts/bin2c; echo "MAGIC_END;") > $@
-targets += config_data.h
-$(obj)/config_data.h: $(obj)/config_data.gz FORCE
- $(call if_changed,ikconfiggz)
diff --git a/kernel/configs.c b/kernel/configs.c
--- a/kernel/configs.c
+++ b/kernel/configs.c
@@ -46,12 +46,20 @@
*/
#define MAGIC_START "IKCFG_ST"
#define MAGIC_END "IKCFG_ED"
-#include "config_data.h"
+asm(
+".section .rodata, \"a\"\n"
+" .ascii \"" MAGIC_START "\"\n"
+"kernel_config_data:\n"
+" .incbin \"kernel/config_data.gz\"\n"
+"kernel_config_data_end:\n"
+" .ascii \"" MAGIC_END "\"\n"
+".previous\n"
+);
-#define MAGIC_SIZE (sizeof(MAGIC_START) - 1)
-#define kernel_config_data_size \
- (sizeof(kernel_config_data) - 1 - MAGIC_SIZE * 2)
+extern const char kernel_config_data[], kernel_config_data_end[];
+
+#define kernel_config_data_size (kernel_config_data_end - kernel_config_data)
#ifdef CONFIG_IKCONFIG_PROC
@@ -69,7 +77,7 @@ ikconfig_read_current(struct file *file,
return 0;
count = min(len, (size_t)(kernel_config_data_size - pos));
- if (copy_to_user(buf, kernel_config_data + MAGIC_SIZE + pos, count))
+ if (copy_to_user(buf, kernel_config_data + pos, count))
return -EFAULT;
*offset += count;
prev parent reply other threads:[~2005-09-25 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 18:30 [PATCH] Use .incbin for config_data.gz Brian Gerst
2005-09-25 10:13 ` Ingo Oeser
2005-09-25 13:16 ` Brian Gerst [this message]
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=4336A332.9010906@didntduck.org \
--to=bgerst@didntduck.org \
--cc=akpm@osdl.org \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox