mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v11 12/14] um: change machine name for uname output
Date: Thu, 18 Sep 2025 14:16:05 +0900	[thread overview]
Message-ID: <8e75e4e2116d25a2bd6065ed6b53e57b0eb0a86f.1758171893.git.thehajime@gmail.com> (raw)
In-Reply-To: <cover.1758171893.git.thehajime@gmail.com>

This commit tries to display MMU/!MMU mode from the output of uname(2)
so that users can distinguish which mode of UML is running right now.

Signed-off-by: Hajime Tazaki <thehajime@gmail.com>
---
 arch/um/Makefile        | 6 ++++++
 arch/um/os-Linux/util.c | 3 ++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/arch/um/Makefile b/arch/um/Makefile
index 5371c9a1b11e..9bc8fc149514 100644
--- a/arch/um/Makefile
+++ b/arch/um/Makefile
@@ -153,6 +153,12 @@ export CFLAGS_vmlinux := $(LINK-y) $(LINK_WRAPS) $(LD_FLAGS_CMDLINE) $(CC_FLAGS_
 CLEAN_FILES += linux x.i gmon.out
 MRPROPER_FILES += $(HOST_DIR)/include/generated
 
+ifeq ($(CONFIG_MMU),y)
+UTS_MACHINE := "um"
+else
+UTS_MACHINE := "um\(nommu\)"
+endif
+
 archclean:
 	@find . \( -name '*.bb' -o -name '*.bbg' -o -name '*.da' \
 		-o -name '*.gcov' \) -type f -print | xargs rm -f
diff --git a/arch/um/os-Linux/util.c b/arch/um/os-Linux/util.c
index 4193e04d7e4a..20421e9f0f77 100644
--- a/arch/um/os-Linux/util.c
+++ b/arch/um/os-Linux/util.c
@@ -65,7 +65,8 @@ void setup_machinename(char *machine_out)
 	}
 # endif
 #endif
-	strcpy(machine_out, host.machine);
+	strcat(machine_out, "/");
+	strcat(machine_out, host.machine);
 }
 
 void setup_hostinfo(char *buf, int len)
-- 
2.43.0


  parent reply	other threads:[~2025-09-18  5:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18  5:15 [PATCH v11 00/14] nommu UML Hajime Tazaki
2025-09-18  5:15 ` [PATCH v11 01/14] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2025-09-18  5:15 ` [PATCH v11 02/14] um: decouple MMU specific code from the common part Hajime Tazaki
2025-09-18  5:15 ` [PATCH v11 03/14] um: nommu: memory handling Hajime Tazaki
2025-09-18  5:15 ` [PATCH v11 04/14] x86/um: nommu: syscall handling Hajime Tazaki
2025-09-18  5:15 ` [PATCH v11 05/14] um: nommu: seccomp syscalls hook Hajime Tazaki
2025-09-18  5:15 ` [PATCH v11 06/14] fixup seccomp Hajime Tazaki
2025-09-18  5:16 ` [PATCH v11 07/14] x86/um: nommu: process/thread handling Hajime Tazaki
2025-09-18  5:16 ` [PATCH v11 08/14] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2025-09-18  5:16 ` [PATCH v11 09/14] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2025-09-18  5:16 ` [PATCH v11 10/14] x86/um: nommu: signal handling Hajime Tazaki
2025-09-18  5:16 ` [PATCH v11 11/14] um: nommu: a work around for MMU dependency to PCI driver Hajime Tazaki
2025-09-18  5:16 ` Hajime Tazaki [this message]
2025-09-18  5:16 ` [PATCH v11 13/14] um: nommu: add documentation of nommu UML Hajime Tazaki
2025-09-18  5:16 ` [PATCH v11 14/14] um: nommu: plug nommu code into build system Hajime Tazaki
2025-09-18  7:38 ` [PATCH v11 00/14] nommu UML 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=8e75e4e2116d25a2bd6065ed6b53e57b0eb0a86f.1758171893.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®