* [PATCH-v2 0/3] rcutorture: minor nolibc fixes
@ 2018-12-29 18:02 Willy Tarreau
2018-12-29 18:02 ` [PATCH 1/4] rcutorture/nolibc: fix the clobbered registers in the MIPS syscall definition Willy Tarreau
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Willy Tarreau @ 2018-12-29 18:02 UTC (permalink / raw)
To: mingo, paulmck; +Cc: rdunlap, linux-kernel, Willy Tarreau
While working on adding some documentation to the nolibc header provided
with rcutorture, I noticed a few accidently deleted lines losing clobbered
registers and some leftover spaces that I fixed. In addition, I finally
added some documentation to the file, as requested by Ingo.
v2: fixed some spelling mistakes after Randy's review
Willy Tarreau (3):
rcutorture/nolibc: fix the clobbered registers in the MIPS syscall
definition
rcutorture/nolibc: fix some poor indentation and alignment
rcutorture/nolibc: add a bit of documentation to explain how to use
nolibc
tools/testing/selftests/rcutorture/bin/nolibc.h | 116 +++++++++++++++++++-----
1 file changed, 91 insertions(+), 25 deletions(-)
--
2.9.0
^ permalink raw reply [flat|nested] 14+ messages in thread* [PATCH 1/4] rcutorture/nolibc: fix the clobbered registers in the MIPS syscall definition 2018-12-29 18:02 [PATCH-v2 0/3] rcutorture: minor nolibc fixes Willy Tarreau @ 2018-12-29 18:02 ` Willy Tarreau 2018-12-29 18:02 ` [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment Willy Tarreau 2018-12-29 18:02 ` [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc Willy Tarreau 2 siblings, 0 replies; 14+ messages in thread From: Willy Tarreau @ 2018-12-29 18:02 UTC (permalink / raw) To: mingo, paulmck; +Cc: rdunlap, linux-kernel, Willy Tarreau A last-minute checkpatch cleanup caused most of list of clobbered registers to be lost in the MIPS syscall definition. As it is right now the code is not used on MIPS, but it's better to fix it before it gets used. Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Signed-off-by: Willy Tarreau <w@1wt.eu> --- tools/testing/selftests/rcutorture/bin/nolibc.h | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tools/testing/selftests/rcutorture/bin/nolibc.h b/tools/testing/selftests/rcutorture/bin/nolibc.h index f98f5b9..30bd27b 100644 --- a/tools/testing/selftests/rcutorture/bin/nolibc.h +++ b/tools/testing/selftests/rcutorture/bin/nolibc.h @@ -1006,7 +1006,7 @@ struct sys_stat_struct { : "=r"(_num), "=r"(_arg4) \ : "r"(_num) \ : "memory", "cc", "at", "v1", "hi", "lo", \ - \ + "t0", "t1", "t2", "t3", "t4", "t5", "t6", "t7", "t8", "t9" \ ); \ _arg4 ? -_num : _num; \ }) @@ -1025,7 +1025,7 @@ struct sys_stat_struct { : "0"(_num), \ "r"(_arg1) \ : "memory", "cc", "at", "v1", "hi", "lo", \ - \ + "t0", "t1", "t2", "t3", "t4", "t5", "t6", "t7", "t8", "t9" \ ); \ _arg4 ? -_num : _num; \ }) @@ -1045,7 +1045,7 @@ struct sys_stat_struct { : "0"(_num), \ "r"(_arg1), "r"(_arg2) \ : "memory", "cc", "at", "v1", "hi", "lo", \ - \ + "t0", "t1", "t2", "t3", "t4", "t5", "t6", "t7", "t8", "t9" \ ); \ _arg4 ? -_num : _num; \ }) @@ -1066,7 +1066,7 @@ struct sys_stat_struct { : "0"(_num), \ "r"(_arg1), "r"(_arg2), "r"(_arg3) \ : "memory", "cc", "at", "v1", "hi", "lo", \ - \ + "t0", "t1", "t2", "t3", "t4", "t5", "t6", "t7", "t8", "t9" \ ); \ _arg4 ? -_num : _num; \ }) @@ -1087,7 +1087,7 @@ struct sys_stat_struct { : "0"(_num), \ "r"(_arg1), "r"(_arg2), "r"(_arg3), "r"(_arg4) \ : "memory", "cc", "at", "v1", "hi", "lo", \ - \ + "t0", "t1", "t2", "t3", "t4", "t5", "t6", "t7", "t8", "t9" \ ); \ _arg4 ? -_num : _num; \ }) @@ -1110,7 +1110,7 @@ struct sys_stat_struct { : "0"(_num), \ "r"(_arg1), "r"(_arg2), "r"(_arg3), "r"(_arg4), "r"(_arg5) \ : "memory", "cc", "at", "v1", "hi", "lo", \ - \ + "t0", "t1", "t2", "t3", "t4", "t5", "t6", "t7", "t8", "t9" \ ); \ _arg4 ? -_num : _num; \ }) -- 2.9.0 ^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment 2018-12-29 18:02 [PATCH-v2 0/3] rcutorture: minor nolibc fixes Willy Tarreau 2018-12-29 18:02 ` [PATCH 1/4] rcutorture/nolibc: fix the clobbered registers in the MIPS syscall definition Willy Tarreau @ 2018-12-29 18:02 ` Willy Tarreau 2018-12-29 22:30 ` Joey Pabalinas 2018-12-29 18:02 ` [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc Willy Tarreau 2 siblings, 1 reply; 14+ messages in thread From: Willy Tarreau @ 2018-12-29 18:02 UTC (permalink / raw) To: mingo, paulmck; +Cc: rdunlap, linux-kernel, Willy Tarreau A few macros had their rightmost backslash misaligned, and the pollfd struct definition resisted the previous code reindent. Nothing else changed. Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Signed-off-by: Willy Tarreau <w@1wt.eu> --- tools/testing/selftests/rcutorture/bin/nolibc.h | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/tools/testing/selftests/rcutorture/bin/nolibc.h b/tools/testing/selftests/rcutorture/bin/nolibc.h index 30bd27b..985364c 100644 --- a/tools/testing/selftests/rcutorture/bin/nolibc.h +++ b/tools/testing/selftests/rcutorture/bin/nolibc.h @@ -81,9 +81,9 @@ typedef signed long time_t; /* for poll() */ struct pollfd { - int fd; - short int events; - short int revents; + int fd; + short int events; + short int revents; }; /* for select() */ @@ -239,7 +239,7 @@ struct stat { "syscall\n" \ : "=a" (_ret) \ : "0"(_num) \ - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ ); \ _ret; \ }) @@ -255,7 +255,7 @@ struct stat { : "=a" (_ret) \ : "r"(_arg1), \ "0"(_num) \ - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ ); \ _ret; \ }) @@ -272,7 +272,7 @@ struct stat { : "=a" (_ret) \ : "r"(_arg1), "r"(_arg2), \ "0"(_num) \ - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ ); \ _ret; \ }) @@ -290,7 +290,7 @@ struct stat { : "=a" (_ret) \ : "r"(_arg1), "r"(_arg2), "r"(_arg3), \ "0"(_num) \ - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ ); \ _ret; \ }) -- 2.9.0 ^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment 2018-12-29 18:02 ` [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment Willy Tarreau @ 2018-12-29 22:30 ` Joey Pabalinas 2018-12-31 19:43 ` Paul E. McKenney 0 siblings, 1 reply; 14+ messages in thread From: Joey Pabalinas @ 2018-12-29 22:30 UTC (permalink / raw) To: Willy Tarreau; +Cc: mingo, paulmck, rdunlap, linux-kernel, Joey Pabalinas [-- Attachment #1: Type: text/plain, Size: 3363 bytes --] On Sat, Dec 29, 2018 at 07:02:17PM +0100, Willy Tarreau wrote: > A few macros had their rightmost backslash misaligned, and the pollfd > struct definition resisted the previous code reindent. Nothing else > changed. > > Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> > Signed-off-by: Willy Tarreau <w@1wt.eu> Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com> > --- > tools/testing/selftests/rcutorture/bin/nolibc.h | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/tools/testing/selftests/rcutorture/bin/nolibc.h b/tools/testing/selftests/rcutorture/bin/nolibc.h > index 30bd27b..985364c 100644 > --- a/tools/testing/selftests/rcutorture/bin/nolibc.h > +++ b/tools/testing/selftests/rcutorture/bin/nolibc.h > @@ -81,9 +81,9 @@ typedef signed long time_t; > > /* for poll() */ > struct pollfd { > - int fd; > - short int events; > - short int revents; > + int fd; > + short int events; > + short int revents; > }; > > /* for select() */ > @@ -239,7 +239,7 @@ struct stat { > "syscall\n" \ > : "=a" (_ret) \ > : "0"(_num) \ > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > ); \ > _ret; \ > }) > @@ -255,7 +255,7 @@ struct stat { > : "=a" (_ret) \ > : "r"(_arg1), \ > "0"(_num) \ > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > ); \ > _ret; \ > }) > @@ -272,7 +272,7 @@ struct stat { > : "=a" (_ret) \ > : "r"(_arg1), "r"(_arg2), \ > "0"(_num) \ > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > ); \ > _ret; \ > }) > @@ -290,7 +290,7 @@ struct stat { > : "=a" (_ret) \ > : "r"(_arg1), "r"(_arg2), "r"(_arg3), \ > "0"(_num) \ > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > ); \ > _ret; \ > }) > -- > 2.9.0 > -- Cheers, Joey Pabalinas [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment 2018-12-29 22:30 ` Joey Pabalinas @ 2018-12-31 19:43 ` Paul E. McKenney 0 siblings, 0 replies; 14+ messages in thread From: Paul E. McKenney @ 2018-12-31 19:43 UTC (permalink / raw) To: Joey Pabalinas, Willy Tarreau, mingo, rdunlap, linux-kernel On Sat, Dec 29, 2018 at 12:30:33PM -1000, Joey Pabalinas wrote: > On Sat, Dec 29, 2018 at 07:02:17PM +0100, Willy Tarreau wrote: > > A few macros had their rightmost backslash misaligned, and the pollfd > > struct definition resisted the previous code reindent. Nothing else > > changed. > > > > Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> > > Signed-off-by: Willy Tarreau <w@1wt.eu> > > Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com> Applied, thank you both! Thanx, Paul > > --- > > tools/testing/selftests/rcutorture/bin/nolibc.h | 14 +++++++------- > > 1 file changed, 7 insertions(+), 7 deletions(-) > > > > diff --git a/tools/testing/selftests/rcutorture/bin/nolibc.h b/tools/testing/selftests/rcutorture/bin/nolibc.h > > index 30bd27b..985364c 100644 > > --- a/tools/testing/selftests/rcutorture/bin/nolibc.h > > +++ b/tools/testing/selftests/rcutorture/bin/nolibc.h > > @@ -81,9 +81,9 @@ typedef signed long time_t; > > > > /* for poll() */ > > struct pollfd { > > - int fd; > > - short int events; > > - short int revents; > > + int fd; > > + short int events; > > + short int revents; > > }; > > > > /* for select() */ > > @@ -239,7 +239,7 @@ struct stat { > > "syscall\n" \ > > : "=a" (_ret) \ > > : "0"(_num) \ > > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > ); \ > > _ret; \ > > }) > > @@ -255,7 +255,7 @@ struct stat { > > : "=a" (_ret) \ > > : "r"(_arg1), \ > > "0"(_num) \ > > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > ); \ > > _ret; \ > > }) > > @@ -272,7 +272,7 @@ struct stat { > > : "=a" (_ret) \ > > : "r"(_arg1), "r"(_arg2), \ > > "0"(_num) \ > > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > ); \ > > _ret; \ > > }) > > @@ -290,7 +290,7 @@ struct stat { > > : "=a" (_ret) \ > > : "r"(_arg1), "r"(_arg2), "r"(_arg3), \ > > "0"(_num) \ > > - : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > + : "rcx", "r8", "r9", "r10", "r11", "memory", "cc" \ > > ); \ > > _ret; \ > > }) > > -- > > 2.9.0 > > > > -- > Cheers, > Joey Pabalinas ^ permalink raw reply [flat|nested] 14+ messages in thread
* [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-29 18:02 [PATCH-v2 0/3] rcutorture: minor nolibc fixes Willy Tarreau 2018-12-29 18:02 ` [PATCH 1/4] rcutorture/nolibc: fix the clobbered registers in the MIPS syscall definition Willy Tarreau 2018-12-29 18:02 ` [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment Willy Tarreau @ 2018-12-29 18:02 ` Willy Tarreau 2018-12-29 22:33 ` Joey Pabalinas 2018-12-29 22:35 ` Randy Dunlap 2 siblings, 2 replies; 14+ messages in thread From: Willy Tarreau @ 2018-12-29 18:02 UTC (permalink / raw) To: mingo, paulmck; +Cc: rdunlap, linux-kernel, Willy Tarreau Ingo rightfully asked for a bit more documentation in the nolibc header, so this patch adds some explanation about its purpose, how it's made, and how to use it. Cc: Ingo Molnar <mingo@kernel.org> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Willy Tarreau <w@1wt.eu> --- tools/testing/selftests/rcutorture/bin/nolibc.h | 90 +++++++++++++++++++++---- 1 file changed, 78 insertions(+), 12 deletions(-) diff --git a/tools/testing/selftests/rcutorture/bin/nolibc.h b/tools/testing/selftests/rcutorture/bin/nolibc.h index 985364c..6643ba9 100644 --- a/tools/testing/selftests/rcutorture/bin/nolibc.h +++ b/tools/testing/selftests/rcutorture/bin/nolibc.h @@ -3,6 +3,84 @@ * Copyright (C) 2017-2018 Willy Tarreau <w@1wt.eu> */ +/* + * This file is designed to be used as a libc alternative for minimal programs + * with very limited requirements. It consists of a small number of syscall and + * type definitions, and the minimal startup code needed to call main(). + * All syscalls are declared as static functions so that they can be optimized + * away by the compiler when not used. + * + * Syscalls are split into 3 levels: + * - the lower level is the arch-specific syscall() definition, consisting in + * assembly code in compound expressions. These are called my_syscall0() to + * my_syscall6() depending on the number of arguments. The MIPS + * implementation is limited to 5 arguments. All input arguments are cast + * to a long stored in a register. These expressions always return the + * syscall's return value as a signed long value which is often either a + * pointer or the negated errno value. + * + * - the second level is mostly architecture-independent. It is made of + * static functions called sys_<name>() which rely on my_syscallN() + * depending on the syscall definition. These functions are responsible + * for exposing the appropriate types for the syscall arguments (int, + * pointers, etc) and for setting the appropriate return type (often int). + * A few of them are architecture-specific because the syscalls are not all + * mapped exactly the same among architectures. For example, some archs do + * not implement select() and need pselect6() instead, so the sys_select() + * function will have to abstract this. + * + * - the third level is the libc call definition. It exposes the lower raw + * sys_<name>() calls in a way that looks like what a libc usually does, + * takes care of specific input values, and of setting errno upon error. + * There can be minor variations compared to standard libc calls. For + * example the open() call always takes 3 args here. + * + * The errno variable is declared static and unused. This way it can be + * optimized away if not used. However this means that a program made of + * multiple C files may observe different errno values (one per C file). For + * the type of programs this project targets it usually is not a problem. The + * resulting program may even be reduced by defining the NOLIBC_IGNORE_ERRNO + * macro, in which case the errno value will never be assigned. + * + * Some stdint-like integer types are defined. These are valid on all currently + * supported architectures, because signs are enforced, ints are assumed to be + * 32 bits, longs the size of a pointer and long long 64 bits. If more + * architectures have to be supported, this may need to be adapted. + * + * Some macro definitions like the O_* values passed to open(), and some + * structures like the sys_stat struct depend on the architecture. + * + * The definitions start with the architecture-specific parts, which are picked + * based on what the compiler knows about the target architecture, and are + * completed with the generic code. Since it is the compiler which sets the + * target architecture, cross-compiling normally works out of the box without + * having to specify anything. + * + * Finally some very common libc-level functions are provided. It is the case + * for a few functions usually found in string.h, ctype.h, or stdlib.h. Nothing + * is currently provided regarding stdio emulation. + * + * The macro NOLIBC is always defined, so that it is possible for a program to + * check this macro to know if it is being built against and decide to disable + * some features or simply not to include some standard libc files. + * + * Ideally this file should be split in multiple files for easier long term + * maintenance, but provided as a single file as it is now, it's quite + * convenient to use. Maybe some variations involving a set of includes at the + * top could work. + * + * A simple static executable may be built this way : + * $ gcc -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \ + * -static -include nolibc.h -lgcc -o hello hello.c + * + * A very useful calling convention table may be found here : + * http://man7.org/linux/man-pages/man2/syscall.2.html + * + * This doc is quite convenient though not necessarily up to date : + * https://w3challs.com/syscalls/ + * + */ + /* some archs (at least aarch64) don't expose the regular syscalls anymore by * default, either because they have an "_at" replacement, or because there are * more modern alternatives. For now we'd rather still use them. @@ -19,18 +97,6 @@ #define NOLIBC -/* Build a static executable this way : - * $ gcc -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \ - * -static -include nolibc.h -lgcc -o hello hello.c - * - * Useful calling convention table found here : - * http://man7.org/linux/man-pages/man2/syscall.2.html - * - * This doc is even better : - * https://w3challs.com/syscalls/ - */ - - /* this way it will be removed if unused */ static int errno; -- 2.9.0 ^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-29 18:02 ` [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc Willy Tarreau @ 2018-12-29 22:33 ` Joey Pabalinas 2018-12-30 7:08 ` Willy Tarreau 2018-12-29 22:35 ` Randy Dunlap 1 sibling, 1 reply; 14+ messages in thread From: Joey Pabalinas @ 2018-12-29 22:33 UTC (permalink / raw) To: Willy Tarreau; +Cc: mingo, paulmck, rdunlap, linux-kernel, Joey Pabalinas [-- Attachment #1: Type: text/plain, Size: 2091 bytes --] On Sat, Dec 29, 2018 at 07:02:18PM +0100, Willy Tarreau wrote: > + * - the lower level is the arch-specific syscall() definition, consisting in > + * assembly code in compound expressions. These are called my_syscall0() to > + * my_syscall6() depending on the number of arguments. The MIPS > + * implementation is limited to 5 arguments. All input arguments are cast > + * to a long stored in a register. These expressions always return the > + * syscall's return value as a signed long value which is often either a > + * pointer or the negated errno value. > + * > + * - the second level is mostly architecture-independent. It is made of > + * static functions called sys_<name>() which rely on my_syscallN() > + * depending on the syscall definition. These functions are responsible > + * for exposing the appropriate types for the syscall arguments (int, > + * pointers, etc) and for setting the appropriate return type (often int). > + * A few of them are architecture-specific because the syscalls are not all > + * mapped exactly the same among architectures. For example, some archs do > + * not implement select() and need pselect6() instead, so the sys_select() > + * function will have to abstract this. > + * > + * - the third level is the libc call definition. It exposes the lower raw > + * sys_<name>() calls in a way that looks like what a libc usually does, > + * takes care of specific input values, and of setting errno upon error. > + * There can be minor variations compared to standard libc calls. For > + * example the open() call always takes 3 args here. Shouldn't these sentences begin with a capitalized "The" for consistency? > /* some archs (at least aarch64) don't expose the regular syscalls anymore by > * default, either because they have an "_at" replacement, or because there are > * more modern alternatives. For now we'd rather still use them. Also here. Shouldn't this begin with a capitalized "Some"? -- Cheers, Joey Pabalinas [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-29 22:33 ` Joey Pabalinas @ 2018-12-30 7:08 ` Willy Tarreau 2018-12-30 7:40 ` Joey Pabalinas 0 siblings, 1 reply; 14+ messages in thread From: Willy Tarreau @ 2018-12-30 7:08 UTC (permalink / raw) To: Joey Pabalinas, mingo, paulmck, rdunlap, linux-kernel On Sat, Dec 29, 2018 at 12:33:24PM -1000, Joey Pabalinas wrote: > On Sat, Dec 29, 2018 at 07:02:18PM +0100, Willy Tarreau wrote: > > + * - the lower level is the arch-specific syscall() definition, consisting in > > + * assembly code in compound expressions. These are called my_syscall0() to > > + * my_syscall6() depending on the number of arguments. The MIPS > > + * implementation is limited to 5 arguments. All input arguments are cast > > + * to a long stored in a register. These expressions always return the > > + * syscall's return value as a signed long value which is often either a > > + * pointer or the negated errno value. > > + * > > + * - the second level is mostly architecture-independent. It is made of > > + * static functions called sys_<name>() which rely on my_syscallN() > > + * depending on the syscall definition. These functions are responsible > > + * for exposing the appropriate types for the syscall arguments (int, > > + * pointers, etc) and for setting the appropriate return type (often int). > > + * A few of them are architecture-specific because the syscalls are not all > > + * mapped exactly the same among architectures. For example, some archs do > > + * not implement select() and need pselect6() instead, so the sys_select() > > + * function will have to abstract this. > > + * > > + * - the third level is the libc call definition. It exposes the lower raw > > + * sys_<name>() calls in a way that looks like what a libc usually does, > > + * takes care of specific input values, and of setting errno upon error. > > + * There can be minor variations compared to standard libc calls. For > > + * example the open() call always takes 3 args here. > > Shouldn't these sentences begin with a capitalized "The" for > consistency? Not sure since they're just list items. But probably as such they should end with a semi-colon and not a dot. Anyway, this is minor and likely for a later update to the file. > > /* some archs (at least aarch64) don't expose the regular syscalls anymore by > > * default, either because they have an "_at" replacement, or because there are > > * more modern alternatives. For now we'd rather still use them. > > Also here. Shouldn't this begin with a capitalized "Some"? Definitely! Same, I won't emit a patch just for this, Paul already queued it. Thanks! Willy ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-30 7:08 ` Willy Tarreau @ 2018-12-30 7:40 ` Joey Pabalinas 2018-12-31 20:08 ` Paul E. McKenney 0 siblings, 1 reply; 14+ messages in thread From: Joey Pabalinas @ 2018-12-30 7:40 UTC (permalink / raw) To: Willy Tarreau; +Cc: Joey Pabalinas, mingo, paulmck, rdunlap, linux-kernel [-- Attachment #1: Type: text/plain, Size: 266 bytes --] On Sun, Dec 30, 2018 at 08:08:46AM +0100, Willy Tarreau wrote: > Definitely! Same, I won't emit a patch just for this, Paul already queued it. Yeah, not that big a deal :) Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com> -- Cheers, Joey Pabalinas [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-30 7:40 ` Joey Pabalinas @ 2018-12-31 20:08 ` Paul E. McKenney 2018-12-31 23:56 ` Willy Tarreau 2019-01-01 0:21 ` Joey Pabalinas 0 siblings, 2 replies; 14+ messages in thread From: Paul E. McKenney @ 2018-12-31 20:08 UTC (permalink / raw) To: Joey Pabalinas, Willy Tarreau, mingo, rdunlap, linux-kernel On Sat, Dec 29, 2018 at 09:40:20PM -1000, Joey Pabalinas wrote: > On Sun, Dec 30, 2018 at 08:08:46AM +0100, Willy Tarreau wrote: > > Definitely! Same, I won't emit a patch just for this, Paul already queued it. > > Yeah, not that big a deal :) > > Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com> But as long as I am rebasing to add the Reviewed-by, might as well update the others. The English rules for capitalization and lists are baroque and completely unsuited to word processors ("If any list item is longer than one line, capitalize all the items."), but in this case each item has multiple sentences, so it makes sense to capitalize. Please see below for the updated commit, and thank you all! And Happy New Year!!! ;-) Thanx, Paul ------------------------------------------------------------------------ commit c12cd600666874ef43f2c555391dce47fe60fcd9 Author: Willy Tarreau <w@1wt.eu> Date: Sat Dec 29 19:02:18 2018 +0100 rcutorture/nolibc: Add a bit of documentation to explain how to use nolibc Ingo rightfully asked for a bit more documentation in the nolibc header, so this patch adds some explanation about its purpose, how it's made, and how to use it. Cc: Ingo Molnar <mingo@kernel.org> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Willy Tarreau <w@1wt.eu> Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com> Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> diff --git a/tools/testing/selftests/rcutorture/bin/nolibc.h b/tools/testing/selftests/rcutorture/bin/nolibc.h index cfbbbad4bca4..1708e9f9f8aa 100644 --- a/tools/testing/selftests/rcutorture/bin/nolibc.h +++ b/tools/testing/selftests/rcutorture/bin/nolibc.h @@ -3,7 +3,85 @@ * Copyright (C) 2017-2018 Willy Tarreau <w@1wt.eu> */ -/* some archs (at least aarch64) don't expose the regular syscalls anymore by +/* + * This file is designed to be used as a libc alternative for minimal programs + * with very limited requirements. It consists of a small number of syscall and + * type definitions, and the minimal startup code needed to call main(). + * All syscalls are declared as static functions so that they can be optimized + * away by the compiler when not used. + * + * Syscalls are split into 3 levels: + * - The lower level is the arch-specific syscall() definition, consisting in + * assembly code in compound expressions. These are called my_syscall0() to + * my_syscall6() depending on the number of arguments. The MIPS + * implementation is limited to 5 arguments. All input arguments are cast + * to a long stored in a register. These expressions always return the + * syscall's return value as a signed long value which is often either a + * pointer or the negated errno value. + * + * - The second level is mostly architecture-independent. It is made of + * static functions called sys_<name>() which rely on my_syscallN() + * depending on the syscall definition. These functions are responsible + * for exposing the appropriate types for the syscall arguments (int, + * pointers, etc) and for setting the appropriate return type (often int). + * A few of them are architecture-specific because the syscalls are not all + * mapped exactly the same among architectures. For example, some archs do + * not implement select() and need pselect6() instead, so the sys_select() + * function will have to abstract this. + * + * - The third level is the libc call definition. It exposes the lower raw + * sys_<name>() calls in a way that looks like what a libc usually does, + * takes care of specific input values, and of setting errno upon error. + * There can be minor variations compared to standard libc calls. For + * example the open() call always takes 3 args here. + * + * The errno variable is declared static and unused. This way it can be + * optimized away if not used. However this means that a program made of + * multiple C files may observe different errno values (one per C file). For + * the type of programs this project targets it usually is not a problem. The + * resulting program may even be reduced by defining the NOLIBC_IGNORE_ERRNO + * macro, in which case the errno value will never be assigned. + * + * Some stdint-like integer types are defined. These are valid on all currently + * supported architectures, because signs are enforced, ints are assumed to be + * 32 bits, longs the size of a pointer and long long 64 bits. If more + * architectures have to be supported, this may need to be adapted. + * + * Some macro definitions like the O_* values passed to open(), and some + * structures like the sys_stat struct depend on the architecture. + * + * The definitions start with the architecture-specific parts, which are picked + * based on what the compiler knows about the target architecture, and are + * completed with the generic code. Since it is the compiler which sets the + * target architecture, cross-compiling normally works out of the box without + * having to specify anything. + * + * Finally some very common libc-level functions are provided. It is the case + * for a few functions usually found in string.h, ctype.h, or stdlib.h. Nothing + * is currently provided regarding stdio emulation. + * + * The macro NOLIBC is always defined, so that it is possible for a program to + * check this macro to know if it is being built against and decide to disable + * some features or simply not to include some standard libc files. + * + * Ideally this file should be split in multiple files for easier long term + * maintenance, but provided as a single file as it is now, it's quite + * convenient to use. Maybe some variations involving a set of includes at the + * top could work. + * + * A simple static executable may be built this way : + * $ gcc -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \ + * -static -include nolibc.h -lgcc -o hello hello.c + * + * A very useful calling convention table may be found here : + * http://man7.org/linux/man-pages/man2/syscall.2.html + * + * This doc is quite convenient though not necessarily up to date : + * https://w3challs.com/syscalls/ + * + */ + +/* Some archs (at least aarch64) don't expose the regular syscalls anymore by * default, either because they have an "_at" replacement, or because there are * more modern alternatives. For now we'd rather still use them. */ @@ -19,18 +97,6 @@ #define NOLIBC -/* Build a static executable this way : - * $ gcc -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \ - * -static -include nolibc.h -lgcc -o hello hello.c - * - * Useful calling convention table found here : - * http://man7.org/linux/man-pages/man2/syscall.2.html - * - * This doc is even better : - * https://w3challs.com/syscalls/ - */ - - /* this way it will be removed if unused */ static int errno; ^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-31 20:08 ` Paul E. McKenney @ 2018-12-31 23:56 ` Willy Tarreau 2019-01-01 0:21 ` Joey Pabalinas 1 sibling, 0 replies; 14+ messages in thread From: Willy Tarreau @ 2018-12-31 23:56 UTC (permalink / raw) To: Paul E. McKenney; +Cc: Joey Pabalinas, mingo, rdunlap, linux-kernel On Mon, Dec 31, 2018 at 12:08:54PM -0800, Paul E. McKenney wrote: > The English rules for capitalization and lists are baroque and completely > unsuited to word processors ("If any list item is longer than one line, > capitalize all the items."), but in this case each item has multiple > sentences, so it makes sense to capitalize. > > Please see below for the updated commit, and thank you all! OK, this looks fine to me, thank you Paul! > And Happy New Year!!! ;-) Oh and same to you ;-) willy ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-31 20:08 ` Paul E. McKenney 2018-12-31 23:56 ` Willy Tarreau @ 2019-01-01 0:21 ` Joey Pabalinas 2019-01-01 17:57 ` Paul E. McKenney 1 sibling, 1 reply; 14+ messages in thread From: Joey Pabalinas @ 2019-01-01 0:21 UTC (permalink / raw) To: Paul E. McKenney Cc: Joey Pabalinas, Willy Tarreau, mingo, rdunlap, linux-kernel [-- Attachment #1: Type: text/plain, Size: 1010 bytes --] On Mon, Dec 31, 2018 at 12:08:54PM -0800, Paul E. McKenney wrote: > On Sat, Dec 29, 2018 at 09:40:20PM -1000, Joey Pabalinas wrote: > > On Sun, Dec 30, 2018 at 08:08:46AM +0100, Willy Tarreau wrote: > > > Definitely! Same, I won't emit a patch just for this, Paul already queued it. > > > > Yeah, not that big a deal :) > > > > Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com> > > But as long as I am rebasing to add the Reviewed-by, might as well > update the others. > > The English rules for capitalization and lists are baroque and completely > unsuited to word processors ("If any list item is longer than one line, > capitalize all the items."), but in this case each item has multiple > sentences, so it makes sense to capitalize. > > Please see below for the updated commit, and thank you all! Interesting, I had no idea it was actually that odd, hah. > And Happy New Year!!! ;-) Glad to help, and happy new year to you as well :) -- Cheers, Joey Pabalinas [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2019-01-01 0:21 ` Joey Pabalinas @ 2019-01-01 17:57 ` Paul E. McKenney 0 siblings, 0 replies; 14+ messages in thread From: Paul E. McKenney @ 2019-01-01 17:57 UTC (permalink / raw) To: Joey Pabalinas, Willy Tarreau, mingo, rdunlap, linux-kernel On Mon, Dec 31, 2018 at 02:21:36PM -1000, Joey Pabalinas wrote: > On Mon, Dec 31, 2018 at 12:08:54PM -0800, Paul E. McKenney wrote: > > On Sat, Dec 29, 2018 at 09:40:20PM -1000, Joey Pabalinas wrote: > > > On Sun, Dec 30, 2018 at 08:08:46AM +0100, Willy Tarreau wrote: > > > > Definitely! Same, I won't emit a patch just for this, Paul already queued it. > > > > > > Yeah, not that big a deal :) > > > > > > Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com> > > > > But as long as I am rebasing to add the Reviewed-by, might as well > > update the others. > > > > The English rules for capitalization and lists are baroque and completely > > unsuited to word processors ("If any list item is longer than one line, > > capitalize all the items."), but in this case each item has multiple > > sentences, so it makes sense to capitalize. > > > > Please see below for the updated commit, and thank you all! > > Interesting, I had no idea it was actually that odd, hah. The horrible thing is the guy that informed me of this had English as his third or fourth of something like seven languages. Yet he knew English better than I ever will. Worst of all, when I would complain about some inconsistency, his response was simply "Mr. McKenney, it is your language, not mine!" ;-) Thanx, Paul ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc 2018-12-29 18:02 ` [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc Willy Tarreau 2018-12-29 22:33 ` Joey Pabalinas @ 2018-12-29 22:35 ` Randy Dunlap 1 sibling, 0 replies; 14+ messages in thread From: Randy Dunlap @ 2018-12-29 22:35 UTC (permalink / raw) To: Willy Tarreau, mingo, paulmck; +Cc: linux-kernel On 12/29/18 10:02 AM, Willy Tarreau wrote: > Ingo rightfully asked for a bit more documentation in the nolibc header, > so this patch adds some explanation about its purpose, how it's made, and > how to use it. > > Cc: Ingo Molnar <mingo@kernel.org> > Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> > Cc: Randy Dunlap <rdunlap@infradead.org> > Signed-off-by: Willy Tarreau <w@1wt.eu> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Thanks. > --- > tools/testing/selftests/rcutorture/bin/nolibc.h | 90 +++++++++++++++++++++---- > 1 file changed, 78 insertions(+), 12 deletions(-) > > diff --git a/tools/testing/selftests/rcutorture/bin/nolibc.h b/tools/testing/selftests/rcutorture/bin/nolibc.h > index 985364c..6643ba9 100644 > --- a/tools/testing/selftests/rcutorture/bin/nolibc.h > +++ b/tools/testing/selftests/rcutorture/bin/nolibc.h > @@ -3,6 +3,84 @@ > * Copyright (C) 2017-2018 Willy Tarreau <w@1wt.eu> > */ > > +/* > + * This file is designed to be used as a libc alternative for minimal programs > + * with very limited requirements. It consists of a small number of syscall and > + * type definitions, and the minimal startup code needed to call main(). > + * All syscalls are declared as static functions so that they can be optimized > + * away by the compiler when not used. > + * > + * Syscalls are split into 3 levels: > + * - the lower level is the arch-specific syscall() definition, consisting in > + * assembly code in compound expressions. These are called my_syscall0() to > + * my_syscall6() depending on the number of arguments. The MIPS > + * implementation is limited to 5 arguments. All input arguments are cast > + * to a long stored in a register. These expressions always return the > + * syscall's return value as a signed long value which is often either a > + * pointer or the negated errno value. > + * > + * - the second level is mostly architecture-independent. It is made of > + * static functions called sys_<name>() which rely on my_syscallN() > + * depending on the syscall definition. These functions are responsible > + * for exposing the appropriate types for the syscall arguments (int, > + * pointers, etc) and for setting the appropriate return type (often int). > + * A few of them are architecture-specific because the syscalls are not all > + * mapped exactly the same among architectures. For example, some archs do > + * not implement select() and need pselect6() instead, so the sys_select() > + * function will have to abstract this. > + * > + * - the third level is the libc call definition. It exposes the lower raw > + * sys_<name>() calls in a way that looks like what a libc usually does, > + * takes care of specific input values, and of setting errno upon error. > + * There can be minor variations compared to standard libc calls. For > + * example the open() call always takes 3 args here. > + * > + * The errno variable is declared static and unused. This way it can be > + * optimized away if not used. However this means that a program made of > + * multiple C files may observe different errno values (one per C file). For > + * the type of programs this project targets it usually is not a problem. The > + * resulting program may even be reduced by defining the NOLIBC_IGNORE_ERRNO > + * macro, in which case the errno value will never be assigned. > + * > + * Some stdint-like integer types are defined. These are valid on all currently > + * supported architectures, because signs are enforced, ints are assumed to be > + * 32 bits, longs the size of a pointer and long long 64 bits. If more > + * architectures have to be supported, this may need to be adapted. > + * > + * Some macro definitions like the O_* values passed to open(), and some > + * structures like the sys_stat struct depend on the architecture. > + * > + * The definitions start with the architecture-specific parts, which are picked > + * based on what the compiler knows about the target architecture, and are > + * completed with the generic code. Since it is the compiler which sets the > + * target architecture, cross-compiling normally works out of the box without > + * having to specify anything. > + * > + * Finally some very common libc-level functions are provided. It is the case > + * for a few functions usually found in string.h, ctype.h, or stdlib.h. Nothing > + * is currently provided regarding stdio emulation. > + * > + * The macro NOLIBC is always defined, so that it is possible for a program to > + * check this macro to know if it is being built against and decide to disable > + * some features or simply not to include some standard libc files. > + * > + * Ideally this file should be split in multiple files for easier long term > + * maintenance, but provided as a single file as it is now, it's quite > + * convenient to use. Maybe some variations involving a set of includes at the > + * top could work. > + * > + * A simple static executable may be built this way : > + * $ gcc -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \ > + * -static -include nolibc.h -lgcc -o hello hello.c > + * > + * A very useful calling convention table may be found here : > + * http://man7.org/linux/man-pages/man2/syscall.2.html > + * > + * This doc is quite convenient though not necessarily up to date : > + * https://w3challs.com/syscalls/ > + * > + */ > + > /* some archs (at least aarch64) don't expose the regular syscalls anymore by > * default, either because they have an "_at" replacement, or because there are > * more modern alternatives. For now we'd rather still use them. > @@ -19,18 +97,6 @@ > > #define NOLIBC > > -/* Build a static executable this way : > - * $ gcc -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \ > - * -static -include nolibc.h -lgcc -o hello hello.c > - * > - * Useful calling convention table found here : > - * http://man7.org/linux/man-pages/man2/syscall.2.html > - * > - * This doc is even better : > - * https://w3challs.com/syscalls/ > - */ > - > - > /* this way it will be removed if unused */ > static int errno; > > -- ~Randy ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2019-01-01 17:57 UTC | newest] Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-12-29 18:02 [PATCH-v2 0/3] rcutorture: minor nolibc fixes Willy Tarreau 2018-12-29 18:02 ` [PATCH 1/4] rcutorture/nolibc: fix the clobbered registers in the MIPS syscall definition Willy Tarreau 2018-12-29 18:02 ` [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment Willy Tarreau 2018-12-29 22:30 ` Joey Pabalinas 2018-12-31 19:43 ` Paul E. McKenney 2018-12-29 18:02 ` [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc Willy Tarreau 2018-12-29 22:33 ` Joey Pabalinas 2018-12-30 7:08 ` Willy Tarreau 2018-12-30 7:40 ` Joey Pabalinas 2018-12-31 20:08 ` Paul E. McKenney 2018-12-31 23:56 ` Willy Tarreau 2019-01-01 0:21 ` Joey Pabalinas 2019-01-01 17:57 ` Paul E. McKenney 2018-12-29 22:35 ` Randy Dunlap
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).