From: Hajime Tazaki <thehajime@gmail.com>
To: linux-um@lists.infradead.org
Cc: thehajime@gmail.com, ricarkol@google.com,
Liam.Howlett@oracle.com, linux-kernel@vger.kernel.org
Subject: [PATCH v14 11/13] um: nommu: disable SMP on nommu UML
Date: Wed, 4 Feb 2026 11:28:09 +0900 [thread overview]
Message-ID: <3b9e3e4b85c9bdbc4e1fdd123c8270652a88e1e9.1770170302.git.thehajime@gmail.com> (raw)
In-Reply-To: <cover.1770170302.git.thehajime@gmail.com>
CONFIG_SMP doesn't work with nommu UML since fs register handling of
host does conflict with thread local storage (more specifically,
the variable signals_enabled).
Thus this commit disables the CONFIG option and the TLS variables.
Signed-off-by: Hajime Tazaki <thehajime@gmail.com>
---
arch/um/os-Linux/internal.h | 8 ++++++++
arch/x86/um/Kconfig | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/um/os-Linux/internal.h b/arch/um/os-Linux/internal.h
index bac9fcc8c14c..25cb5cc931c1 100644
--- a/arch/um/os-Linux/internal.h
+++ b/arch/um/os-Linux/internal.h
@@ -6,6 +6,14 @@
#include <stub-data.h>
#include <signal.h>
+/* NOMMU doesn't work with thread-local storage used in CONFIG_SMP,
+ * due to the dependency on host_fs variable switch upon user/kernel
+ * context so, disable TLS until NOMMU supports SMP.
+ */
+#ifndef CONFIG_MMU
+#define __thread
+#endif
+
/*
* elf_aux.c
*/
diff --git a/arch/x86/um/Kconfig b/arch/x86/um/Kconfig
index bdd7c8e39b01..f12e2e4e0a12 100644
--- a/arch/x86/um/Kconfig
+++ b/arch/x86/um/Kconfig
@@ -12,7 +12,7 @@ config UML_X86
select ARCH_USE_QUEUED_SPINLOCKS
select DCACHE_WORD_ACCESS
select HAVE_EFFICIENT_UNALIGNED_ACCESS
- select UML_SUBARCH_SUPPORTS_SMP if X86_CX8
+ select UML_SUBARCH_SUPPORTS_SMP if X86_CX8 && MMU
config 64BIT
bool "64-bit kernel" if "$(SUBARCH)" = "x86"
--
2.43.0
next prev parent reply other threads:[~2026-02-04 2:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 2:27 [PATCH v14 00/13] " Hajime Tazaki
2026-02-04 2:27 ` [PATCH v14 01/13] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 02/13] um: decouple MMU specific code from the common part Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 03/13] um: nommu: memory handling Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 04/13] x86/um: nommu: syscall handling Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 05/13] um: nommu: seccomp syscalls hook Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 06/13] x86/um: nommu: process/thread handling Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 07/13] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 08/13] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 09/13] x86/um: nommu: signal handling Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 10/13] um: change machine name for uname output Hajime Tazaki
2026-02-04 2:28 ` Hajime Tazaki [this message]
2026-02-04 2:28 ` [PATCH v14 12/13] um: nommu: add documentation of nommu UML Hajime Tazaki
2026-02-04 2:28 ` [PATCH v14 13/13] um: nommu: plug nommu code into build system Hajime Tazaki
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=3b9e3e4b85c9bdbc4e1fdd123c8270652a88e1e9.1770170302.git.thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=ricarkol@google.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®