From: Hajime Tazaki <thehajime@gmail.com> To: linux-um@lists.infradead.org Cc: Octavian Purdila <tavi.purdila@gmail.com>, Akira Moroo <retrage01@gmail.com>, linux-kernel-library@freelists.org, linux-arch@vger.kernel.org Subject: [RFC v2 33/37] kallsyms: Add a config option to select section for kallsyms Date: Fri, 8 Nov 2019 14:02:48 +0900 [thread overview] Message-ID: <1f8a9e18edf808f2016899887a3110be63cbc3c1.1573179553.git.thehajime@gmail.com> (raw) In-Reply-To: <cover.1573179553.git.thehajime@gmail.com> From: Andreas Abel <aabel@google.com> This commit adds a kernel config option to select whether the kallsyms data should be in the .rodata section (the default for non-LKL builds), or in the .data section (the default for LKL). This is to avoid relocations in the text segment (TEXTRELs) that would otherwise occur with LKL when the .rodata and the .text section end up in the same segment. Having TEXTRELs can lead to a number of issues: 1. If a shared library contains a TEXTREL, the corresponding memory pages cannot be shared. 2. Android >=6 and SELinux do not support binaries with TEXTRELs (http://android-developers.blogspot.com/2016/06/android-changes-for-ndk-developers.html). 3. If a program has a TEXTREL, uses an ifunc, and is compiled with early binding, this can lead to a segmentation fault when processing the relocation for the ifunc during dynamic linking because the text segment is made temporarily non-executable to process the TEXTREL (line 248 in dl_reloc.c). Signed-off-by: Andreas Abel <aabel@google.com> --- init/Kconfig | 12 ++++++++++++ scripts/kallsyms.c | 11 +++++++++-- scripts/link-vmlinux.sh | 4 ++++ 3 files changed, 25 insertions(+), 2 deletions(-) diff --git a/init/Kconfig b/init/Kconfig index 81293d78a6ad..bd1a846e0ee0 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -1385,6 +1385,18 @@ config POSIX_TIMERS If unsure say y. +config KALLSYMS_USE_DATA_SECTION + bool "Use .data instead of .rodata section for kallsyms" + depends on KALLSYMS + default n + help + Enabling this option will put the kallsyms data in the .data section + instead of the .rodata section. + + This is useful when building the kernel as a library, as it avoids + relocations in the text segment that could otherwise occur if the + .rodata section is in the same segment as the .text section. + config PRINTK default y bool "Enable support for printk" if EXPERT diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c index 75ec25554111..5e4f270c3904 100644 --- a/scripts/kallsyms.c +++ b/scripts/kallsyms.c @@ -59,6 +59,7 @@ static struct addr_range percpu_range = { static struct sym_entry *table; static unsigned int table_size, table_cnt; static int all_symbols = 0; +static int use_data_section; static int absolute_percpu = 0; static char symbol_prefix_char = '\0'; static int base_relative = 0; @@ -74,6 +75,7 @@ static void usage(void) { fprintf(stderr, "Usage: kallsyms [--all-symbols] " "[--symbol-prefix=<prefix char>] " + "[--use-data-section] " "[--base-relative] < in.map > out.S\n"); exit(1); } @@ -362,7 +364,10 @@ static void write_src(void) printf("#define ALGN .balign 4\n"); printf("#endif\n"); - printf("\t.section .rodata, \"a\"\n"); + if (use_data_section) + printf("\t.section .data\n"); + else + printf("\t.section .rodata, \"a\"\n"); /* Provide proper symbols relocatability by their relativeness * to a fixed anchor point in the runtime image, either '_text' @@ -774,7 +779,9 @@ int main(int argc, char **argv) if ((*p == '"' && *(p+2) == '"') || (*p == '\'' && *(p+2) == '\'')) p++; symbol_prefix_char = *p; - } else + } else if (strcmp(argv[i], "--use-data-section") == 0) + use_data_section = 1; + else usage(); } } else if (argc != 1) diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh index 553d966a1986..3fc1fc406b38 100755 --- a/scripts/link-vmlinux.sh +++ b/scripts/link-vmlinux.sh @@ -133,6 +133,10 @@ kallsyms() kallsymopt="${kallsymopt} --base-relative" fi + if [ -n "${CONFIG_KALLSYMS_USE_DATA_SECTION}" ]; then + kallsymopt="${kallsymopt} --use-data-section" + fi + local aflags="${KBUILD_AFLAGS} ${KBUILD_AFLAGS_KERNEL} \ ${NOSTDINC_FLAGS} ${LINUXINCLUDE} ${KBUILD_CPPFLAGS}" -- 2.20.1 (Apple Git-117)
WARNING: multiple messages have this Message-ID (diff)
From: Hajime Tazaki <thehajime@gmail.com> To: linux-um@lists.infradead.org Cc: Octavian Purdila <tavi.purdila@gmail.com>, linux-kernel-library@freelists.org, linux-arch@vger.kernel.org, Akira Moroo <retrage01@gmail.com> Subject: [RFC v2 33/37] kallsyms: Add a config option to select section for kallsyms Date: Fri, 8 Nov 2019 14:02:48 +0900 [thread overview] Message-ID: <1f8a9e18edf808f2016899887a3110be63cbc3c1.1573179553.git.thehajime@gmail.com> (raw) In-Reply-To: <cover.1573179553.git.thehajime@gmail.com> From: Andreas Abel <aabel@google.com> This commit adds a kernel config option to select whether the kallsyms data should be in the .rodata section (the default for non-LKL builds), or in the .data section (the default for LKL). This is to avoid relocations in the text segment (TEXTRELs) that would otherwise occur with LKL when the .rodata and the .text section end up in the same segment. Having TEXTRELs can lead to a number of issues: 1. If a shared library contains a TEXTREL, the corresponding memory pages cannot be shared. 2. Android >=6 and SELinux do not support binaries with TEXTRELs (http://android-developers.blogspot.com/2016/06/android-changes-for-ndk-developers.html). 3. If a program has a TEXTREL, uses an ifunc, and is compiled with early binding, this can lead to a segmentation fault when processing the relocation for the ifunc during dynamic linking because the text segment is made temporarily non-executable to process the TEXTREL (line 248 in dl_reloc.c). Signed-off-by: Andreas Abel <aabel@google.com> --- init/Kconfig | 12 ++++++++++++ scripts/kallsyms.c | 11 +++++++++-- scripts/link-vmlinux.sh | 4 ++++ 3 files changed, 25 insertions(+), 2 deletions(-) diff --git a/init/Kconfig b/init/Kconfig index 81293d78a6ad..bd1a846e0ee0 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -1385,6 +1385,18 @@ config POSIX_TIMERS If unsure say y. +config KALLSYMS_USE_DATA_SECTION + bool "Use .data instead of .rodata section for kallsyms" + depends on KALLSYMS + default n + help + Enabling this option will put the kallsyms data in the .data section + instead of the .rodata section. + + This is useful when building the kernel as a library, as it avoids + relocations in the text segment that could otherwise occur if the + .rodata section is in the same segment as the .text section. + config PRINTK default y bool "Enable support for printk" if EXPERT diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c index 75ec25554111..5e4f270c3904 100644 --- a/scripts/kallsyms.c +++ b/scripts/kallsyms.c @@ -59,6 +59,7 @@ static struct addr_range percpu_range = { static struct sym_entry *table; static unsigned int table_size, table_cnt; static int all_symbols = 0; +static int use_data_section; static int absolute_percpu = 0; static char symbol_prefix_char = '\0'; static int base_relative = 0; @@ -74,6 +75,7 @@ static void usage(void) { fprintf(stderr, "Usage: kallsyms [--all-symbols] " "[--symbol-prefix=<prefix char>] " + "[--use-data-section] " "[--base-relative] < in.map > out.S\n"); exit(1); } @@ -362,7 +364,10 @@ static void write_src(void) printf("#define ALGN .balign 4\n"); printf("#endif\n"); - printf("\t.section .rodata, \"a\"\n"); + if (use_data_section) + printf("\t.section .data\n"); + else + printf("\t.section .rodata, \"a\"\n"); /* Provide proper symbols relocatability by their relativeness * to a fixed anchor point in the runtime image, either '_text' @@ -774,7 +779,9 @@ int main(int argc, char **argv) if ((*p == '"' && *(p+2) == '"') || (*p == '\'' && *(p+2) == '\'')) p++; symbol_prefix_char = *p; - } else + } else if (strcmp(argv[i], "--use-data-section") == 0) + use_data_section = 1; + else usage(); } } else if (argc != 1) diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh index 553d966a1986..3fc1fc406b38 100755 --- a/scripts/link-vmlinux.sh +++ b/scripts/link-vmlinux.sh @@ -133,6 +133,10 @@ kallsyms() kallsymopt="${kallsymopt} --base-relative" fi + if [ -n "${CONFIG_KALLSYMS_USE_DATA_SECTION}" ]; then + kallsymopt="${kallsymopt} --use-data-section" + fi + local aflags="${KBUILD_AFLAGS} ${KBUILD_AFLAGS_KERNEL} \ ${NOSTDINC_FLAGS} ${LINUXINCLUDE} ${KBUILD_CPPFLAGS}" -- 2.20.1 (Apple Git-117) _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2019-11-08 5:04 UTC|newest] Thread overview: 206+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-23 4:37 [RFC PATCH 00/47] Unifying LKL into UML Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 01/47] asm-generic: atomic64: allow using generic atomic64 on 64bit platforms Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 02/47] kbuild: allow architectures to automatically define kconfig symbols Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 03/47] lkl: architecture skeleton for Linux kernel library Hajime Tazaki 2019-10-25 21:40 ` Richard Weinberger 2019-10-27 2:36 ` Hajime Tazaki 2019-10-29 4:04 ` Lai Jiangshan 2019-10-29 7:13 ` Hajime Tazaki 2019-10-29 7:57 ` Johannes Berg 2019-10-29 8:15 ` Richard Weinberger 2019-10-30 3:19 ` Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 04/47] lkl: host interface Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 05/47] lkl: memory handling Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 06/47] lkl: kernel threads support Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 07/47] lkl: interrupt support Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 08/47] lkl: system call interface and application API Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 09/47] lkl: timers, time and delay support Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 10/47] lkl: memory mapped I/O support Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 11/47] lkl: basic kernel console support Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 12/47] lkl: initialization and cleanup Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 13/47] lkl: plug in the build system Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 14/47] lkl tools: skeleton for host side library, tests and tools Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 15/47] lkl tools: host lib: add utilities functions Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 16/47] lkl tools: host lib: memory mapped I/O helpers Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 17/47] lkl tools: host lib: virtio devices Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 18/47] lkl tools: host lib: virtio block device Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 19/47] lkl tools: host lib: filesystem helpers Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 20/47] lkl tools: host lib: posix host operations Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 21/47] lkl tools: "boot" test Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 22/47] lkl tools: tool that converts a filesystem image to tar Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 23/47] lkl tools: tool that reads/writes to/from a filesystem image Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 24/47] lkl tools: virtio: add network device support Hajime Tazaki 2019-10-23 4:37 ` [RFC PATCH 25/47] lkl: add support for Windows hosts Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 26/47] lkl tools: add support for Windows host Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 27/47] lkl: Android ARM (arm/arm64) support Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 28/47] lkl tools: add lklfuse Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 29/47] lkl: add initial system call hijack support (a.k.a. NUSE of libos) Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 30/47] lkl: add documentation Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 31/47] cpu: add cpu_yield_to_irqs Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 32/47] tools: Add the lkl host library to the common tools Makefile Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 33/47] signal: use CONFIG_X86_32 instead of __i386__ Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 34/47] arch: add __SYSCALL_DEFINE_ARCH Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 35/47] xfs: support for non-mmu architectures Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 36/47] checkpatch: avoid showing BIT_ULL warnings for tools/ files Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 37/47] Revert "vmlinux.lds.h: remove stale <linux/export.h> include" Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 38/47] Revert "export.h: remove code for prefixing symbols with underscore" Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 39/47] Revert "linux/linkage.h: replace VMLINUX_SYMBOL_STR() with __stringify()" Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 40/47] Revert "vmlinux.lds.h: remove no-op macro VMLINUX_SYMBOL()" Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 41/47] Revert "kbuild: remove CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX" Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 42/47] Revert "kallsyms: remove symbol prefix support" Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 43/47] kallsyms: Add a config option to select section for kallsyms Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 44/47] um lkl: use ARCH=um SUBARCH=lkl for tools/lkl Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 45/47] um lkl: add CI tests Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 46/47] um: use lkl virtio_net_tap device as UML device Hajime Tazaki 2019-10-23 4:38 ` [RFC PATCH 47/47] um: add lkl virtio-blk device Hajime Tazaki 2019-10-25 21:34 ` [RFC PATCH 00/47] Unifying LKL into UML Richard Weinberger 2019-10-25 21:34 ` Richard Weinberger 2019-10-27 2:34 ` Hajime Tazaki 2019-10-27 2:34 ` Hajime Tazaki 2019-10-29 7:57 ` Johannes Berg 2019-10-29 15:45 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 00/37] " Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 01/37] asm-generic: atomic64: allow using generic atomic64 on 64bit platforms Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-25 22:02 ` Richard Weinberger 2019-11-25 22:02 ` Richard Weinberger 2019-11-26 14:02 ` Hajime Tazaki 2019-11-26 14:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 02/37] arch: add __SYSCALL_DEFINE_ARCH Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-25 22:02 ` Richard Weinberger 2019-11-25 22:02 ` Richard Weinberger 2019-11-27 4:15 ` Hajime Tazaki 2019-11-27 4:15 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 03/37] lkl: architecture skeleton for Linux kernel library Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-25 22:00 ` Richard Weinberger 2019-11-25 22:00 ` Richard Weinberger 2019-11-26 11:42 ` Octavian Purdila 2019-11-26 11:42 ` Octavian Purdila 2019-11-26 14:17 ` Hajime Tazaki 2019-11-26 14:17 ` Hajime Tazaki 2019-11-26 16:02 ` Richard Weinberger 2019-11-26 16:02 ` Richard Weinberger 2020-02-05 7:37 ` Hajime Tazaki 2020-02-05 7:37 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 04/37] lkl: host interface Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 05/37] lkl: memory handling Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-25 22:10 ` Richard Weinberger 2019-11-25 22:10 ` Richard Weinberger 2020-02-05 7:38 ` Hajime Tazaki 2020-02-05 7:38 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 06/37] lkl: kernel threads support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 07/37] lkl: interrupt support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-25 22:13 ` Richard Weinberger 2019-11-25 22:13 ` Richard Weinberger 2020-02-05 7:38 ` Hajime Tazaki 2020-02-05 7:38 ` Hajime Tazaki 2020-02-05 10:49 ` Anton Ivanov 2020-02-05 10:49 ` Anton Ivanov 2020-02-05 14:24 ` Hajime Tazaki 2020-02-05 14:24 ` Hajime Tazaki 2020-02-18 8:18 ` Hajime Tazaki 2020-02-18 8:18 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 08/37] lkl: system call interface and application API Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 09/37] lkl: timers, time and delay support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 10/37] lkl: memory mapped I/O support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 11/37] lkl: basic kernel console support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 12/37] lkl: initialization and cleanup Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 13/37] lkl: plug in the build system Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 14/37] lkl tools: skeleton for host side library, tests and tools Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 15/37] lkl tools: host lib: add utilities functions Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 16/37] lkl tools: host lib: memory mapped I/O helpers Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 17/37] lkl tools: host lib: virtio devices Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-25 22:07 ` Richard Weinberger 2019-11-25 22:07 ` Richard Weinberger 2019-11-26 8:43 ` Johannes Berg 2019-11-26 8:43 ` Johannes Berg 2019-11-26 8:50 ` Richard Weinberger 2019-11-26 8:50 ` Richard Weinberger 2019-11-26 8:52 ` Johannes Berg 2019-11-26 8:52 ` Johannes Berg 2019-11-26 10:09 ` Richard Weinberger 2019-11-26 10:09 ` Richard Weinberger 2019-11-26 10:16 ` Johannes Berg 2019-11-26 10:16 ` Johannes Berg 2019-11-26 10:42 ` Octavian Purdila 2019-11-26 10:42 ` Octavian Purdila 2019-11-26 10:49 ` Anton Ivanov 2019-11-26 10:49 ` Anton Ivanov 2019-11-27 4:06 ` Hajime Tazaki 2019-11-27 4:06 ` Hajime Tazaki 2019-11-26 16:04 ` Richard Weinberger 2019-11-26 16:04 ` Richard Weinberger 2019-11-27 4:08 ` Hajime Tazaki 2019-11-27 4:08 ` Hajime Tazaki 2019-11-27 14:28 ` Richard Weinberger 2019-11-27 14:28 ` Richard Weinberger 2019-11-28 9:53 ` Hajime Tazaki 2019-11-28 9:53 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 18/37] lkl tools: host lib: virtio block device Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 19/37] lkl tools: host lib: filesystem helpers Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 20/37] lkl tools: host lib: posix host operations Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 21/37] lkl tools: "boot" test Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2020-01-23 19:33 ` Brendan Higgins 2020-01-24 4:32 ` Hajime Tazaki 2020-01-24 4:32 ` Hajime Tazaki 2020-03-02 19:51 ` Luis Chamberlain 2020-03-02 19:51 ` Luis Chamberlain 2020-03-02 22:25 ` Brendan Higgins 2020-03-02 22:25 ` Brendan Higgins 2019-11-08 5:02 ` [RFC v2 22/37] lkl tools: tool that reads/writes to/from a filesystem image Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 23/37] lkl tools: tool that converts a filesystem image to tar Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 24/37] lkl tools: virtio: add network device support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 25/37] checkpatch: avoid showing BIT_ULL warnings for tools/ files Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 26/37] tools: Add the lkl host library to the common tools Makefile Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 27/37] lkl tools: add lklfuse Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 28/37] lkl: add system call hijack support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 29/37] lkl: add documentation Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 30/37] scripts: revert CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX patches Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 31/37] lkl: add support for Windows hosts Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 32/37] lkl tools: add support for Windows host Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki [this message] 2019-11-08 5:02 ` [RFC v2 33/37] kallsyms: Add a config option to select section for kallsyms Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 34/37] lkl: Android ARM (arm/arm64) support Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 35/37] um lkl: add CI tests Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 36/37] um: use lkl virtio_net_tap device as UML device Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 5:02 ` [RFC v2 37/37] um: add lkl virtio-blk device Hajime Tazaki 2019-11-08 5:02 ` Hajime Tazaki 2019-11-08 9:13 ` [RFC v2 00/37] Unifying LKL into UML Anton Ivanov 2019-11-08 9:13 ` Anton Ivanov 2019-11-08 11:17 ` Octavian Purdila 2019-11-08 11:17 ` Octavian Purdila
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=1f8a9e18edf808f2016899887a3110be63cbc3c1.1573179553.git.thehajime@gmail.com \ --to=thehajime@gmail.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel-library@freelists.org \ --cc=linux-um@lists.infradead.org \ --cc=retrage01@gmail.com \ --cc=tavi.purdila@gmail.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: linkBe 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.