Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Benjamin Berg <benjamin@sipsolutions.net>
Cc: linux-um@lists.infradead.org, Willy Tarreau <w@1wt.eu>,
	 linux-kselftest@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	 linux-kernel@vger.kernel.org,
	Benjamin Berg <benjamin.berg@intel.com>
Subject: Re: [PATCH v3 08/12] um: add infrastructure to build files using nolibc
Date: Thu, 25 Sep 2025 18:36:36 +0200	[thread overview]
Message-ID: <43a71f2c-2d3d-4b66-b755-d182eefc90d2@t-8ch.de> (raw)
In-Reply-To: <20250924142059.527768-9-benjamin@sipsolutions.net>

On 2025-09-24 16:20:55+0200, Benjamin Berg wrote:
> From: Benjamin Berg <benjamin.berg@intel.com>
> 
> Add NOLIBC_CFLAGS and NOLIBC_OBJS to build files against nolibc rather
> than libc. With this it is possible to move to nolibc in smaller steps.
> 
> Set NOLIBC_IGNORE_ERRNO, as the nolibc errno implementation is overly
> simple and cannot handle threading. nolibc provides sys_* functions that
> do not emulate the libc errno behaviour and can be used instead.
> 
> Leave the syscall definition for kernel code for now, but guard it as it
> is a macro in nolibc.
> 
> Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
> 
> ---
> v3:
> - Change the syscall guard to use __KERNEL__
> 
> v2:
> - Do not include nolibc.h via CFLAGS
> - Make syscall guard more explicit
> - Remove __UM_NOLIBC__ define, it is not needed
> - Fix out-of-tree building
> ---
>  arch/um/Makefile               | 20 +++++++++++++++++++-
>  arch/um/include/shared/os.h    |  2 ++
>  arch/um/include/shared/user.h  |  1 -
>  arch/um/scripts/Makefile.rules |  8 +++++++-
>  4 files changed, 28 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/um/Makefile b/arch/um/Makefile
> index f7c509262568..c3a81df50911 100644
> --- a/arch/um/Makefile
> +++ b/arch/um/Makefile
> @@ -78,6 +78,24 @@ USER_CFLAGS = $(patsubst $(KERNEL_DEFINES),,$(patsubst -I%,,$(KBUILD_CFLAGS))) \
>  		-include $(srctree)/include/linux/kern_levels.h \
>  		-include $(srctree)/$(ARCH_DIR)/include/shared/user.h
>  
> +NOLIBC_CFLAGS = $(patsubst $(KERNEL_DEFINES),,$(patsubst -I%,,$(KBUILD_CFLAGS))) \
> +		$(ARCH_INCLUDE) $(MODE_INCLUDE) $(filter -I%,$(CFLAGS)) \
> +		-I $(srctree)/tools/include \
> +		-D__EXPORTED_HEADERS__ \
> +		-D__UM_HOST__ \
> +		-DNOLIBC_NO_RUNTIME \
> +		-DNOLIBC_IGNORE_ERRNO \
> +		-nostdlib -nostdinc -static \
> +		-I$(srctree)/include/uapi \
> +		-I$(srctree)/$(HOST_DIR)/include/uapi \
> +		-I$(objtree)/$(HOST_DIR)/include/generated/uapi \
> +		-I $(srctree)/tools/include/nolibc \
> +		-I $(srctree)/usr/include \

This looks incorrect. The UAPI headers would be installed to $(objtree).
But UML does not even use CONFIG_HEADERS_INSTALL.
Also the whitespace is inconsistent between different lines.

> +		-include $(objtree)/include/generated/autoconf.h \
> +		-include $(srctree)/tools/include/linux/kconfig.h \
> +		-include $(srctree)/include/linux/kern_levels.h \
> +		-include $(srctree)/$(ARCH_DIR)/include/shared/user.h
> +
>  #This will adjust *FLAGS accordingly to the platform.
>  include $(srctree)/$(ARCH_DIR)/Makefile-os-Linux
>  
> @@ -160,4 +178,4 @@ archclean:
>  		-o -name '*.gcov' \) -type f -print | xargs rm -f
>  	$(Q)$(MAKE) -f $(srctree)/Makefile ARCH=$(HEADER_ARCH) clean
>  
> -export HEADER_ARCH SUBARCH USER_CFLAGS CFLAGS_NO_HARDENING DEV_NULL_PATH
> +export HEADER_ARCH SUBARCH USER_CFLAGS NOLIBC_CFLAGS CFLAGS_NO_HARDENING DEV_NULL_PATH

(...)

  reply	other threads:[~2025-09-25 16:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 14:20 [PATCH v3 00/12] Start porting UML to nolibc Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 01/12] tools compiler.h: fix __used definition Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 02/12] um: use tools/include for user files Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 03/12] tools/nolibc/stdio: let perror work when NOLIBC_IGNORE_ERRNO is set Benjamin Berg
2025-09-25 16:22   ` Thomas Weißschuh
2025-09-24 14:20 ` [PATCH v3 04/12] tools/nolibc/dirent: avoid errno in readdir_r Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 05/12] tools/nolibc: implement %m if errno is not defined Benjamin Berg
2025-09-25 16:24   ` Thomas Weißschuh
2025-09-24 14:20 ` [PATCH v3 06/12] tools/nolibc: use __fallthrough__ rather than fallthrough Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 07/12] tools/nolibc: add option to disable runtime Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 08/12] um: add infrastructure to build files using nolibc Benjamin Berg
2025-09-25 16:36   ` Thomas Weißschuh [this message]
2025-09-24 14:20 ` [PATCH v3 09/12] um: use nolibc for the --showconfig implementation Benjamin Berg
2025-09-26 12:57   ` kernel test robot
2025-10-20 14:21     ` Thomas Weißschuh
2025-10-29 14:07       ` Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 10/12] tools/nolibc: add uio.h with readv and writev Benjamin Berg
2025-09-24 14:20 ` [PATCH v3 11/12] tools/nolibc: add ptrace support Benjamin Berg
2025-09-25 16:28   ` Thomas Weißschuh
2025-09-24 14:20 ` [PATCH v3 12/12] um: switch ptrace FP register access to nolibc Benjamin Berg

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=43a71f2c-2d3d-4b66-b755-d182eefc90d2@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=acme@redhat.com \
    --cc=benjamin.berg@intel.com \
    --cc=benjamin@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=w@1wt.eu \
    /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